Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a770ff7a5b3c1ac3d8788ce202142d73e24c0dd5a5e12858f7c4c3e3e21ee758

Tx prefix hash: 459fe499252fcc271320bb62aee266cf955ffb7ec26d83d96aa74187d39afaf6
Tx public key: 802eb9d168db7ca8cb8013b5284df6b615231bd8f0db144e51901e0646955f6e
Timestamp: 1718175067 Timestamp [UCT]: 2024-06-12 06:51:07 Age [y:d:h:m:s]: 00:275:09:02:25
Block: 1042433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196797 RingCT/type: yes/0
Extra: 01802eb9d168db7ca8cb8013b5284df6b615231bd8f0db144e51901e0646955f6e02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d14beff1aa9ea8ed10a84f47f8e919b07581b82f76e36b34d752495b75ff1fdb 0.600000000000 1511350 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": 1042443, "vin": [ { "gen": { "height": 1042433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d14beff1aa9ea8ed10a84f47f8e919b07581b82f76e36b34d752495b75ff1fdb" } } ], "extra": [ 1, 128, 46, 185, 209, 104, 219, 124, 168, 203, 128, 19, 181, 40, 77, 246, 182, 21, 35, 27, 216, 240, 219, 20, 78, 81, 144, 30, 6, 70, 149, 95, 110, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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