Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38bc53ad868e607b8129a68eb711d907deab302b13083f5cab09937d832dc0e9

Tx prefix hash: 4cf2e48cbf3c48d72ccb2623b31c3a5404b5c7d716657619880f56a58e712a86
Tx public key: 7213484d02390e608d53307be8f196b0cd5fa9173c768d2dcaf15257235aa9f6
Timestamp: 1709653394 Timestamp [UCT]: 2024-03-05 15:43:14 Age [y:d:h:m:s]: 01:250:13:28:22
Block: 971787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437781 RingCT/type: yes/0
Extra: 017213484d02390e608d53307be8f196b0cd5fa9173c768d2dcaf15257235aa9f602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b04e197b6fc625f3a7db07da14b06198b0f6f77455b9990ac76c7ac6dcb32ecc 0.600000000000 1431688 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": 971797, "vin": [ { "gen": { "height": 971787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b04e197b6fc625f3a7db07da14b06198b0f6f77455b9990ac76c7ac6dcb32ecc" } } ], "extra": [ 1, 114, 19, 72, 77, 2, 57, 14, 96, 141, 83, 48, 123, 232, 241, 150, 176, 205, 95, 169, 23, 60, 118, 141, 45, 202, 241, 82, 87, 35, 90, 169, 246, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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