Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75c38f3a5fc7d2b32fd9467d2fd1d57676b3b1341226320e6d0d75642ab77f3

Tx prefix hash: 47219fe5c39a6afe5875c4732a5197719e73f19739b06aea97005f5c2740893c
Tx public key: 442e9f01155f4b4094b5642959f3954c16dc27228db5cb88bad4214b2c171caa
Timestamp: 1752531879 Timestamp [UCT]: 2025-07-14 22:24:39 Age [y:d:h:m:s]: 00:172:22:11:53
Block: 1325603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122398 RingCT/type: yes/0
Extra: 01442e9f01155f4b4094b5642959f3954c16dc27228db5cb88bad4214b2c171caa021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 498fb358019c8e26418f372dee9ae9b9ceacc1e33db2e9630b1b8fa8dfa5ead6 0.600000000000 1813350 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": 1325613, "vin": [ { "gen": { "height": 1325603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "498fb358019c8e26418f372dee9ae9b9ceacc1e33db2e9630b1b8fa8dfa5ead6" } } ], "extra": [ 1, 68, 46, 159, 1, 21, 95, 75, 64, 148, 181, 100, 41, 89, 243, 149, 76, 22, 220, 39, 34, 141, 181, 203, 136, 186, 212, 33, 75, 44, 23, 28, 170, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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