Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a8476a5928baf6d3fbcc23747abb0feb6ea1038c412567257eae44fa14b0d9c

Tx prefix hash: 5fdf734ffc6b74905721e64c14ca7569fcdba70e2cb4e635dddb9914dcf6f7fd
Tx public key: 33dbf0b0dac7dc81a626fc55f8ab2349d697e6b111591d97e57a0a186d71b431
Timestamp: 1735921804 Timestamp [UCT]: 2025-01-03 16:30:04 Age [y:d:h:m:s]: 00:166:13:04:59
Block: 1189434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118705 RingCT/type: yes/0
Extra: 0133dbf0b0dac7dc81a626fc55f8ab2349d697e6b111591d97e57a0a186d71b4310211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 534697a0783ecd7dd642795851970509ccc13e817e98933c62c9387513fdad79 0.600000000000 1675943 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": 1189444, "vin": [ { "gen": { "height": 1189434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "534697a0783ecd7dd642795851970509ccc13e817e98933c62c9387513fdad79" } } ], "extra": [ 1, 51, 219, 240, 176, 218, 199, 220, 129, 166, 38, 252, 85, 248, 171, 35, 73, 214, 151, 230, 177, 17, 89, 29, 151, 229, 122, 10, 24, 109, 113, 180, 49, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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