Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d20d48bbb984546aa0b0301628a251449d374bbe651a7e6c05cfd4be9de6ba2

Tx prefix hash: 4519ec9e2d3f3b2648e00ac1525d3ee614f24d419f48148cc98e30497a327c0f
Tx public key: 03e4b7b3f59e1990fa547dc4f7f82f8c17514d7d182f30f4d85a9088712b8e32
Timestamp: 1710262929 Timestamp [UCT]: 2024-03-12 17:02:09 Age [y:d:h:m:s]: 01:250:21:37:36
Block: 976844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438027 RingCT/type: yes/0
Extra: 0103e4b7b3f59e1990fa547dc4f7f82f8c17514d7d182f30f4d85a9088712b8e320211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bd2f7aee0ad774b2011c917a5471c6137afd7dfbcd7b62c22b6d1dc5d3a8305 0.600000000000 1436841 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": 976854, "vin": [ { "gen": { "height": 976844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bd2f7aee0ad774b2011c917a5471c6137afd7dfbcd7b62c22b6d1dc5d3a8305" } } ], "extra": [ 1, 3, 228, 183, 179, 245, 158, 25, 144, 250, 84, 125, 196, 247, 248, 47, 140, 23, 81, 77, 125, 24, 47, 48, 244, 216, 90, 144, 136, 113, 43, 142, 50, 2, 17, 0, 0, 0, 17, 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