Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 432616bc91bcb6bd9a44fd94a5a9fedebb81cbfc1206e732afbb7394fe9ce41c

Tx prefix hash: 459ccecc83288cd1e21e61d867aae327921bd10c1e1f378c73ebee72e5ef545b
Tx public key: e8d75ec74b7c844d043fabcc16e82b3d940840de322b9d8709eaef62d4e9a896
Timestamp: 1755022817 Timestamp [UCT]: 2025-08-12 18:20:17 Age [y:d:h:m:s]: 00:054:00:46:55
Block: 1345604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37889 RingCT/type: yes/0
Extra: 01e8d75ec74b7c844d043fabcc16e82b3d940840de322b9d8709eaef62d4e9a896021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 268db6e5dd02372871c71077f27efdba3e2956c82ba95a3ccbe55a6fde9be746 0.600000000000 1833499 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": 1345614, "vin": [ { "gen": { "height": 1345604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "268db6e5dd02372871c71077f27efdba3e2956c82ba95a3ccbe55a6fde9be746" } } ], "extra": [ 1, 232, 215, 94, 199, 75, 124, 132, 77, 4, 63, 171, 204, 22, 232, 43, 61, 148, 8, 64, 222, 50, 43, 157, 135, 9, 234, 239, 98, 212, 233, 168, 150, 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