Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec7df3dc45cde14c1436fb95380043a5d4790ce635b8107dfdb8475b7a2c9206

Tx prefix hash: df8c38722b8cc41d60d3798ebe8eb7a3db656e88041bfc71a798fd17e93bd914
Tx public key: 5e38d5264aaceea193e6149e61e5be4fe53068da0652fc569d3e9d8e9bc128b6
Timestamp: 1717796022 Timestamp [UCT]: 2024-06-07 21:33:42 Age [y:d:h:m:s]: 00:282:02:03:17
Block: 1039284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201600 RingCT/type: yes/0
Extra: 015e38d5264aaceea193e6149e61e5be4fe53068da0652fc569d3e9d8e9bc128b602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d64540674811e7891b04af3cec5ec5d5268385de0a74ea3327e4d313b93377b 0.600000000000 1507917 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": 1039294, "vin": [ { "gen": { "height": 1039284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d64540674811e7891b04af3cec5ec5d5268385de0a74ea3327e4d313b93377b" } } ], "extra": [ 1, 94, 56, 213, 38, 74, 172, 238, 161, 147, 230, 20, 158, 97, 229, 190, 79, 229, 48, 104, 218, 6, 82, 252, 86, 157, 62, 157, 142, 155, 193, 40, 182, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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