Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c733e21a0e5227ec03d0602cbd0e41d71bd99e2c4fc4c274d4f15de5bcf2687a

Tx prefix hash: a7a0f9080698d9432478e0e9a32cb48341b366370836463bb7f1f5d8f3970935
Tx public key: 6cf02debe94d43b80947ae3ad2f674dd0f6fdebc3286b124b96f5bbedead43cd
Timestamp: 1757609527 Timestamp [UCT]: 2025-09-11 16:52:07 Age [y:d:h:m:s]: 00:058:11:01:00
Block: 1366237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41869 RingCT/type: yes/0
Extra: 016cf02debe94d43b80947ae3ad2f674dd0f6fdebc3286b124b96f5bbedead43cd021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0c99b658906a603f0b058197dd571f31c81281ae22820b5496412735a42a793 0.600000000000 1854276 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": 1366247, "vin": [ { "gen": { "height": 1366237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0c99b658906a603f0b058197dd571f31c81281ae22820b5496412735a42a793" } } ], "extra": [ 1, 108, 240, 45, 235, 233, 77, 67, 184, 9, 71, 174, 58, 210, 246, 116, 221, 15, 111, 222, 188, 50, 134, 177, 36, 185, 111, 91, 190, 222, 173, 67, 205, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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