Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7052ab04d8e227f4f850a54ea65e695457fb1472701528b896fc5f6d4594142

Tx prefix hash: 427fb7a77aeda6df5715c75fab3763d702e6f08b583d5026448cdaeafafeab69
Tx public key: 337db6d16b06db577dc783cabca21713b3cf6e86e62bc6146d57818cb4d4347a
Timestamp: 1717665537 Timestamp [UCT]: 2024-06-06 09:18:57 Age [y:d:h:m:s]: 01:240:00:47:21
Block: 1038203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430052 RingCT/type: yes/0
Extra: 01337db6d16b06db577dc783cabca21713b3cf6e86e62bc6146d57818cb4d4347a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14977fdb1f21f0e5e6796d1db3d9d9ac6a08e3db2b42d3e1e36a7e0bada680f9 0.600000000000 1506764 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": 1038213, "vin": [ { "gen": { "height": 1038203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14977fdb1f21f0e5e6796d1db3d9d9ac6a08e3db2b42d3e1e36a7e0bada680f9" } } ], "extra": [ 1, 51, 125, 182, 209, 107, 6, 219, 87, 125, 199, 131, 202, 188, 162, 23, 19, 179, 207, 110, 134, 230, 43, 198, 20, 109, 87, 129, 140, 180, 212, 52, 122, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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