Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6529fb0770b3c50f21c019d5effcd6dc26ece33d4a2f01bf6cd534ccdd59b5

Tx prefix hash: b4f3aedcbe9bb54488208f1dc13c3a17299288876cceea71d5bc46d95a0664b5
Tx public key: 4c49c2a416f728e68f44788328457a37be4068edf233698d1b954d877f68ceda
Timestamp: 1710599041 Timestamp [UCT]: 2024-03-16 14:24:01 Age [y:d:h:m:s]: 01:023:21:51:57
Block: 979632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278066 RingCT/type: yes/0
Extra: 014c49c2a416f728e68f44788328457a37be4068edf233698d1b954d877f68ceda0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e524580392c6129664b3d54acb79aba9ad5e60eb6f424f4c7fc7acaff0b20bfd 0.600000000000 1439675 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": 979642, "vin": [ { "gen": { "height": 979632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e524580392c6129664b3d54acb79aba9ad5e60eb6f424f4c7fc7acaff0b20bfd" } } ], "extra": [ 1, 76, 73, 194, 164, 22, 247, 40, 230, 143, 68, 120, 131, 40, 69, 122, 55, 190, 64, 104, 237, 242, 51, 105, 141, 27, 149, 77, 135, 127, 104, 206, 218, 2, 17, 0, 0, 0, 5, 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