Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 323ec5eb78b1ea1c573e1f071499ed3124ed90735f2d4306002beb338ef1d107

Tx prefix hash: 196baf0a2c626a2de3e0a98cba094946399488a4e6a31b9944c2d5b1434ac73b
Tx public key: 1abf1d56b4179ca3c0acd251bef07211fdfe83e4ece387e00181e095245a3a64
Timestamp: 1754098412 Timestamp [UCT]: 2025-08-02 01:33:32 Age [y:d:h:m:s]: 00:063:17:45:16
Block: 1338406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44376 RingCT/type: yes/0
Extra: 011abf1d56b4179ca3c0acd251bef07211fdfe83e4ece387e00181e095245a3a64021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c16674721edc7d48e4107986e67152749a6a5a097407f8ef763de91c6f751c 0.600000000000 1826215 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": 1338416, "vin": [ { "gen": { "height": 1338406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c16674721edc7d48e4107986e67152749a6a5a097407f8ef763de91c6f751c" } } ], "extra": [ 1, 26, 191, 29, 86, 180, 23, 156, 163, 192, 172, 210, 81, 190, 240, 114, 17, 253, 254, 131, 228, 236, 227, 135, 224, 1, 129, 224, 149, 36, 90, 58, 100, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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