Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad6e69ecd3c07b202cfca00e50f32d7624bb3fe201ff0be22d8bdec2201d682

Tx prefix hash: 22d6f6636e8b2883b0523a2a3a1b1357020ea81882f3ca4a74e900c8ca4dd24c
Tx public key: 160f7cb1960c0c060cc0a7968cb31cc30ecd7cf8418e7f198aa3fd62a10f1b99
Timestamp: 1751832391 Timestamp [UCT]: 2025-07-06 20:06:31 Age [y:d:h:m:s]: 00:135:18:08:20
Block: 1320146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95425 RingCT/type: yes/0
Extra: 01160f7cb1960c0c060cc0a7968cb31cc30ecd7cf8418e7f198aa3fd62a10f1b99021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec688b08bf43dade693dce601643a391b0b0ad76d6c9d15a8363927ecaa310c0 0.600000000000 1807841 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": 1320156, "vin": [ { "gen": { "height": 1320146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec688b08bf43dade693dce601643a391b0b0ad76d6c9d15a8363927ecaa310c0" } } ], "extra": [ 1, 22, 15, 124, 177, 150, 12, 12, 6, 12, 192, 167, 150, 140, 179, 28, 195, 14, 205, 124, 248, 65, 142, 127, 25, 138, 163, 253, 98, 161, 15, 27, 153, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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