Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c050fd401ae9c329d9e1c9a27031b4ab130fd962f3d07107447c5b362de35a7

Tx prefix hash: b62a79309cf3ed28268feab8cfd9d750689330f1cf1c460b2477d65ce87fc121
Tx public key: 8f5485bed252c7f193a874c4166faa1431762d5a6e018291c11d047b84c4ba1e
Timestamp: 1764735818 Timestamp [UCT]: 2025-12-03 04:23:38 Age [y:d:h:m:s]: 00:000:22:24:23
Block: 1425308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664 RingCT/type: yes/0
Extra: 018f5485bed252c7f193a874c4166faa1431762d5a6e018291c11d047b84c4ba1e02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cea420df1b6565f179c3c4d41aa40d59c551a9344a4b90e8adfac5adf8163550 0.600000000000 1913941 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": 1425318, "vin": [ { "gen": { "height": 1425308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cea420df1b6565f179c3c4d41aa40d59c551a9344a4b90e8adfac5adf8163550" } } ], "extra": [ 1, 143, 84, 133, 190, 210, 82, 199, 241, 147, 168, 116, 196, 22, 111, 170, 20, 49, 118, 45, 90, 110, 1, 130, 145, 193, 29, 4, 123, 132, 196, 186, 30, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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