Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464568e16fc8245bad239a51c992f7a821fd607e8409859f5f6a3bddcc8f43ea

Tx prefix hash: 37bc40876a631960a1caf169531a82eac846f0ca46fcfae1bf4586fcb301c8d5
Tx public key: eab44047e5dff0fee1dc9be19d4c4f25cd84c40dbbefd9f69d813e59fc4d9be8
Timestamp: 1580836797 Timestamp [UCT]: 2020-02-04 17:19:57 Age [y:d:h:m:s]: 05:034:07:12:18
Block: 58641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176534 RingCT/type: yes/0
Extra: 01eab44047e5dff0fee1dc9be19d4c4f25cd84c40dbbefd9f69d813e59fc4d9be80211000000118a2ee0d9000000000000000000

1 output(s) for total of 392.372755388000 dcy

stealth address amount amount idx
00: 46a57029198e5dee8ba7a1cda8ae15f82f06860f07c52e0cbb66ccadd52293b9 392.372755388000 108357 of 0

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": 58651, "vin": [ { "gen": { "height": 58641 } } ], "vout": [ { "amount": 392372755388, "target": { "key": "46a57029198e5dee8ba7a1cda8ae15f82f06860f07c52e0cbb66ccadd52293b9" } } ], "extra": [ 1, 234, 180, 64, 71, 229, 223, 240, 254, 225, 220, 155, 225, 157, 76, 79, 37, 205, 132, 196, 13, 187, 239, 217, 246, 157, 129, 62, 89, 252, 77, 155, 232, 2, 17, 0, 0, 0, 17, 138, 46, 224, 217, 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