Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a21d9a3b7ec684d8f53a25e2ac6b7653e4d09a725ab41016312f3d89734da5bd

Tx prefix hash: 228e9b9612bcf240cc813ba783a171a02c11d678838ca43bf7407d9b72cf71c5
Tx public key: f326a1a86e52e1b74f5a25c826458e6f0e7b4160d9e00ff8da571f6f30749c64
Timestamp: 1706456224 Timestamp [UCT]: 2024-01-28 15:37:04 Age [y:d:h:m:s]: 01:105:08:37:05
Block: 945243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336410 RingCT/type: yes/0
Extra: 01f326a1a86e52e1b74f5a25c826458e6f0e7b4160d9e00ff8da571f6f30749c6402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 971c0a4ea7193f45ea16d10a68335a86205369561568ab3397272900acfcec5b 0.600000000000 1403553 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": 945253, "vin": [ { "gen": { "height": 945243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "971c0a4ea7193f45ea16d10a68335a86205369561568ab3397272900acfcec5b" } } ], "extra": [ 1, 243, 38, 161, 168, 110, 82, 225, 183, 79, 90, 37, 200, 38, 69, 142, 111, 14, 123, 65, 96, 217, 224, 15, 248, 218, 87, 31, 111, 48, 116, 156, 100, 2, 17, 0, 0, 0, 1, 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