Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afb5d5641716a811ba11ab5ae62aa33f1efc567db66a0842d167a676e713d0ba

Tx prefix hash: ee076ba5ac3624bbafde252256504da0de6011982e03ba94f8b4e2037b4e8dcd
Tx public key: 4af8d30292e4ab7c34b128a1897d8054d2d94dbab9df1321f591e3017036dd98
Timestamp: 1745035591 Timestamp [UCT]: 2025-04-19 04:06:31 Age [y:d:h:m:s]: 00:216:20:15:29
Block: 1264596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152711 RingCT/type: yes/0
Extra: 014af8d30292e4ab7c34b128a1897d8054d2d94dbab9df1321f591e3017036dd980211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d0d0ab7ce6049570212aca52f6d95f2c739399b00b9c3dd19fb9a30b78dc0f 0.600000000000 1751795 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": 1264606, "vin": [ { "gen": { "height": 1264596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d0d0ab7ce6049570212aca52f6d95f2c739399b00b9c3dd19fb9a30b78dc0f" } } ], "extra": [ 1, 74, 248, 211, 2, 146, 228, 171, 124, 52, 177, 40, 161, 137, 125, 128, 84, 210, 217, 77, 186, 185, 223, 19, 33, 245, 145, 227, 1, 112, 54, 221, 152, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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