Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56d12ef9f433867d67f3448050535661048c4f0a0c219a47d0a3233feafb7ae

Tx prefix hash: 5e60ba4ee14d314eb7c50bc8214df061fb20319c95f8719bada9279737c2e358
Tx public key: 4e21ceb7c78e3992e1cf5da5bb88bb5587d5cc72a02b049a48ac25ac76f2bb8a
Timestamp: 1747623607 Timestamp [UCT]: 2025-05-19 03:00:07 Age [y:d:h:m:s]: 00:142:02:18:04
Block: 1286027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99193 RingCT/type: yes/0
Extra: 014e21ceb7c78e3992e1cf5da5bb88bb5587d5cc72a02b049a48ac25ac76f2bb8a0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2e19ee278a681eab1b2428758df5be8b43176aebf483658d0e47ebcfc6f1daa 0.600000000000 1773492 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": 1286037, "vin": [ { "gen": { "height": 1286027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2e19ee278a681eab1b2428758df5be8b43176aebf483658d0e47ebcfc6f1daa" } } ], "extra": [ 1, 78, 33, 206, 183, 199, 142, 57, 146, 225, 207, 93, 165, 187, 136, 187, 85, 135, 213, 204, 114, 160, 43, 4, 154, 72, 172, 37, 172, 118, 242, 187, 138, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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