Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0162cc80640ae65cd923756083b1e543d9d58601fcb5e305f71a4a91972862c5

Tx prefix hash: 3efd161613f4c4a12288eaee6bd96d154b254ecab251a88c8677be31a121d56a
Tx public key: 908c6cfa00bc30bb9ccf5b9be971820674046f5f4bb3337fa72f7bf8c4d8ce70
Timestamp: 1751835180 Timestamp [UCT]: 2025-07-06 20:53:00 Age [y:d:h:m:s]: 00:131:03:53:42
Block: 1320156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92156 RingCT/type: yes/0
Extra: 01908c6cfa00bc30bb9ccf5b9be971820674046f5f4bb3337fa72f7bf8c4d8ce7002110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d5d4e8b0fd7414852b309443a019ea3d764f9564094e3a62b34e1cc042eb894 0.600000000000 1807851 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": 1320166, "vin": [ { "gen": { "height": 1320156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d5d4e8b0fd7414852b309443a019ea3d764f9564094e3a62b34e1cc042eb894" } } ], "extra": [ 1, 144, 140, 108, 250, 0, 188, 48, 187, 156, 207, 91, 155, 233, 113, 130, 6, 116, 4, 111, 95, 75, 179, 51, 127, 167, 47, 123, 248, 196, 216, 206, 112, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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