Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f56ac6caba944bca87a578adc5c97a9a1a7ef6fae275c58b608e37096cf499

Tx prefix hash: ef832cb56134022afdc6163326a4ef49fe69274cc6a6666f0f8a6e47842c64b3
Tx public key: a5bb09c3bdc45fcb4d36c61470d63e676f0e8cf3f9eff3d8669279ae71e8890c
Timestamp: 1731737350 Timestamp [UCT]: 2024-11-16 06:09:10 Age [y:d:h:m:s]: 00:008:01:42:09
Block: 1154778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5771 RingCT/type: yes/0
Extra: 01a5bb09c3bdc45fcb4d36c61470d63e676f0e8cf3f9eff3d8669279ae71e8890c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e94d091dc04ef177a0fdefb4fa87887f51b694d120e8a00101da195f1237c89 0.600000000000 1640391 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": 1154788, "vin": [ { "gen": { "height": 1154778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e94d091dc04ef177a0fdefb4fa87887f51b694d120e8a00101da195f1237c89" } } ], "extra": [ 1, 165, 187, 9, 195, 189, 196, 95, 203, 77, 54, 198, 20, 112, 214, 62, 103, 111, 14, 140, 243, 249, 239, 243, 216, 102, 146, 121, 174, 113, 232, 137, 12, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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