Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c4c80216ebaf30a73952218be06ed8be947780be704ca9f7e38097d24f39a6fb

Tx prefix hash: b736a65a2ca9cf56ea61db334888c329a598bfc7670db851b4cf5a2db3c2c30d
Tx public key: f48d2f397882e065750d686b46afe2faab77e2a584b0298a66fd165a8df108b9
Timestamp: 1722571762 Timestamp [UCT]: 2024-08-02 04:09:22 Age [y:d:h:m:s]: 00:299:17:54:36
Block: 1078873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214172 RingCT/type: yes/0
Extra: 01f48d2f397882e065750d686b46afe2faab77e2a584b0298a66fd165a8df108b902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fedb7c38b4726270959c7b82388032ab170a511c5a2893a10aeb610168e5eaf4 0.600000000000 1551588 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1078883, "vin": [ { "gen": { "height": 1078873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fedb7c38b4726270959c7b82388032ab170a511c5a2893a10aeb610168e5eaf4" } } ], "extra": [ 1, 244, 141, 47, 57, 120, 130, 224, 101, 117, 13, 104, 107, 70, 175, 226, 250, 171, 119, 226, 165, 132, 176, 41, 138, 102, 253, 22, 90, 141, 241, 8, 185, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8