Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f5021bd65565335d45e82f0b2db6df4915da26e45d496745f04600e80ac532c

Tx prefix hash: b0136ab2a6221f3349ee0a757a819a1c76f5ff5a7ef5140ab76aa9ca0ded5a8a
Tx public key: 879a298223d608edc8e170827ac0b28e1f625f1c27a8731feddb6a773ce985d7
Timestamp: 1718667024 Timestamp [UCT]: 2024-06-17 23:30:24 Age [y:d:h:m:s]: 00:218:16:24:23
Block: 1046502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156447 RingCT/type: yes/0
Extra: 01879a298223d608edc8e170827ac0b28e1f625f1c27a8731feddb6a773ce985d70211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56d1eaf6fdf47865f1f05c0eca8c0277b438162ee5f5f75e999ed9924532d182 0.600000000000 1516317 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": 1046512, "vin": [ { "gen": { "height": 1046502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56d1eaf6fdf47865f1f05c0eca8c0277b438162ee5f5f75e999ed9924532d182" } } ], "extra": [ 1, 135, 154, 41, 130, 35, 214, 8, 237, 200, 225, 112, 130, 122, 192, 178, 142, 31, 98, 95, 28, 39, 168, 115, 31, 237, 219, 106, 119, 60, 233, 133, 215, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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