Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eadd87768f03dea8409683346a29ab2ec3ff7b26a2ac7e5aadd6f9388775be1d

Tx prefix hash: 03baa4aef507cee82b4a111538f284b4c5514f1a6499b59c7a59fec4edb5551c
Tx public key: bf2d64e840173a03904fdd733fc2690bd79acdf3deb846f1b0992c896371e59d
Timestamp: 1732727252 Timestamp [UCT]: 2024-11-27 17:07:32 Age [y:d:h:m:s]: 00:133:21:38:49
Block: 1162974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95511 RingCT/type: yes/0
Extra: 01bf2d64e840173a03904fdd733fc2690bd79acdf3deb846f1b0992c896371e59d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10eae7264c8f540d38d83f4721e959ffebf730b87d63d23187e66161fb4a969a 0.600000000000 1648637 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": 1162984, "vin": [ { "gen": { "height": 1162974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10eae7264c8f540d38d83f4721e959ffebf730b87d63d23187e66161fb4a969a" } } ], "extra": [ 1, 191, 45, 100, 232, 64, 23, 58, 3, 144, 79, 221, 115, 63, 194, 105, 11, 215, 154, 205, 243, 222, 184, 70, 241, 176, 153, 44, 137, 99, 113, 229, 157, 2, 17, 0, 0, 0, 4, 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