Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511505dcc89253fcf140be3d5a9a3ba0b2ba6440186234e44c2d3ea0dffabee8

Tx prefix hash: d00ffe601544fcfd753c0ab0c24911b139f702831bac59451a77542441b164f1
Tx public key: 60e012f2ee71a89ef7e7144b039e53e7e5737164c7524e05782556d500ac933a
Timestamp: 1706267616 Timestamp [UCT]: 2024-01-26 11:13:36 Age [y:d:h:m:s]: 00:289:19:02:22
Block: 943678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207516 RingCT/type: yes/0
Extra: 0160e012f2ee71a89ef7e7144b039e53e7e5737164c7524e05782556d500ac933a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9a85295b5a1c12c0919c15f3fa6af9a374aa7d9a5540acdb5d3fb17c7727560 0.600000000000 1401886 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": 943688, "vin": [ { "gen": { "height": 943678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9a85295b5a1c12c0919c15f3fa6af9a374aa7d9a5540acdb5d3fb17c7727560" } } ], "extra": [ 1, 96, 224, 18, 242, 238, 113, 168, 158, 247, 231, 20, 75, 3, 158, 83, 231, 229, 115, 113, 100, 199, 82, 78, 5, 120, 37, 86, 213, 0, 172, 147, 58, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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