Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2553dd79b86366d56d84c2879b403d04c9e93fe4d6dfaf04122b1f9f85f8d0a

Tx prefix hash: 291bc3d8a35a778c24a420b28600cffd52110f493f77d273327d9edd61992391
Tx public key: 9a3cf0d7ab36a08b873cf91c72ebab49179e7ade84079e4fdcfe276e7c8b572e
Timestamp: 1725123646 Timestamp [UCT]: 2024-08-31 17:00:46 Age [y:d:h:m:s]: 00:222:16:29:53
Block: 1100034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159009 RingCT/type: yes/0
Extra: 019a3cf0d7ab36a08b873cf91c72ebab49179e7ade84079e4fdcfe276e7c8b572e02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ec33f1a6358c49373681dbf51ed8221d780541a92606e0209ab98c414de5a10 0.600000000000 1576005 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": 1100044, "vin": [ { "gen": { "height": 1100034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ec33f1a6358c49373681dbf51ed8221d780541a92606e0209ab98c414de5a10" } } ], "extra": [ 1, 154, 60, 240, 215, 171, 54, 160, 139, 135, 60, 249, 28, 114, 235, 171, 73, 23, 158, 122, 222, 132, 7, 158, 79, 220, 254, 39, 110, 124, 139, 87, 46, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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