Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d4647da2c3d148179511e2c144f8bc073a68696a8f1229c05e2ddbec30869a

Tx prefix hash: e1253023c3b605dbabef3f03ffb7bf7340042b9a6bb2920c7d6bac703376daa6
Tx public key: 20cab2ca8fcd85a5b54e0b650dc3b69e8db12b41e52acd60e1c923ab4e03fcbf
Timestamp: 1729054392 Timestamp [UCT]: 2024-10-16 04:53:12 Age [y:d:h:m:s]: 00:150:00:39:14
Block: 1132644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106981 RingCT/type: yes/0
Extra: 0120cab2ca8fcd85a5b54e0b650dc3b69e8db12b41e52acd60e1c923ab4e03fcbf0211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cba7231aeff8b170e2e45ef2fcac4c7a1eb569d34df8e28d3fa7bf63930ef1b 0.600000000000 1615607 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": 1132654, "vin": [ { "gen": { "height": 1132644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cba7231aeff8b170e2e45ef2fcac4c7a1eb569d34df8e28d3fa7bf63930ef1b" } } ], "extra": [ 1, 32, 202, 178, 202, 143, 205, 133, 165, 181, 78, 11, 101, 13, 195, 182, 158, 141, 177, 43, 65, 229, 42, 205, 96, 225, 201, 35, 171, 78, 3, 252, 191, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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