Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a61a9f89b461c755d6765ea757eecd1cb66a55d16391cafb66e6a6d87ed4a79b

Tx prefix hash: 4e6ffc936d882c9f1f2f50b5a01f391e932f555fdfe67aa6771bd57e430d6842
Tx public key: e9ef2b9d0cf38646ce1454771f21126d75d3608a32115940b2eccd9fe1ef3739
Timestamp: 1713633034 Timestamp [UCT]: 2024-04-20 17:10:34 Age [y:d:h:m:s]: 00:218:12:11:57
Block: 1004762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156421 RingCT/type: yes/0
Extra: 01e9ef2b9d0cf38646ce1454771f21126d75d3608a32115940b2eccd9fe1ef37390211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428b172c6c7c7534bb18a4cf2ba03edf0e0e4abb8d1581471fdf7bba9636502e 0.600000000000 1465336 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": 1004772, "vin": [ { "gen": { "height": 1004762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428b172c6c7c7534bb18a4cf2ba03edf0e0e4abb8d1581471fdf7bba9636502e" } } ], "extra": [ 1, 233, 239, 43, 157, 12, 243, 134, 70, 206, 20, 84, 119, 31, 33, 18, 109, 117, 211, 96, 138, 50, 17, 89, 64, 178, 236, 205, 159, 225, 239, 55, 57, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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