Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5244c62bea2215e8e9bd386bf9a3bd3d1ccab5cd5078908d3c249df04526fcc1

Tx prefix hash: c79efd1c5efcb4c630117491dcbe61d4b04283e81bb58788f4121455c89a66b6
Tx public key: 17bb539f7471556b9675912871a2c1b59a3131c16fa8d5ed2eab3fa72157c1b8
Timestamp: 1703000292 Timestamp [UCT]: 2023-12-19 15:38:12 Age [y:d:h:m:s]: 01:324:00:17:50
Block: 916621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490411 RingCT/type: yes/0
Extra: 0117bb539f7471556b9675912871a2c1b59a3131c16fa8d5ed2eab3fa72157c1b802110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e305cbdc304f3628f3ef10a77a21b02a094e199fd85fc52f72743cf627790d8 0.600000000000 1374179 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": 916631, "vin": [ { "gen": { "height": 916621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e305cbdc304f3628f3ef10a77a21b02a094e199fd85fc52f72743cf627790d8" } } ], "extra": [ 1, 23, 187, 83, 159, 116, 113, 85, 107, 150, 117, 145, 40, 113, 162, 193, 181, 154, 49, 49, 193, 111, 168, 213, 237, 46, 171, 63, 167, 33, 87, 193, 184, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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