Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3d398eaf21e29e307a548e336c0acff7d87894814376e12c14ad0ef48cfeecf

Tx prefix hash: 8e881d3b461dfadab5ba06d772211fc778b64d992bbde6376ff5d3fad3d1e443
Tx public key: 97b18ff9c322384712437aed83bde9dd530f7c5caeafde05c6f8a38f8bab0aa4
Timestamp: 1731757509 Timestamp [UCT]: 2024-11-16 11:45:09 Age [y:d:h:m:s]: 00:141:04:57:41
Block: 1154947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100724 RingCT/type: yes/0
Extra: 0197b18ff9c322384712437aed83bde9dd530f7c5caeafde05c6f8a38f8bab0aa4021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b68e1318104cf858caa8ab22eed2c0895e4400491f2bca0eb8579968f07e123 0.600000000000 1640560 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": 1154957, "vin": [ { "gen": { "height": 1154947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b68e1318104cf858caa8ab22eed2c0895e4400491f2bca0eb8579968f07e123" } } ], "extra": [ 1, 151, 177, 143, 249, 195, 34, 56, 71, 18, 67, 122, 237, 131, 189, 233, 221, 83, 15, 124, 92, 174, 175, 222, 5, 198, 248, 163, 143, 139, 171, 10, 164, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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