Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba1f012135ba6bdf178002ddc0065cd5d73afa83bd3cb54ea991f3c43592316c

Tx prefix hash: 395d1c9b9efc326d6bb65a8abc46069a4321516b5d17a56045407bc5a67d065b
Tx public key: 9903313ecaf519057b192e9fbca72bdca9c8c8a3955963d5ec132884c495fdae
Timestamp: 1748913535 Timestamp [UCT]: 2025-06-03 01:18:55 Age [y:d:h:m:s]: 00:164:09:26:46
Block: 1296715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115177 RingCT/type: yes/0
Extra: 019903313ecaf519057b192e9fbca72bdca9c8c8a3955963d5ec132884c495fdae021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d8cd963f2da25c8d8f3a00f85505d7ae3f68740d482d60a49bb4753c0edab29 0.600000000000 1784230 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": 1296725, "vin": [ { "gen": { "height": 1296715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d8cd963f2da25c8d8f3a00f85505d7ae3f68740d482d60a49bb4753c0edab29" } } ], "extra": [ 1, 153, 3, 49, 62, 202, 245, 25, 5, 123, 25, 46, 159, 188, 167, 43, 220, 169, 200, 200, 163, 149, 89, 99, 213, 236, 19, 40, 132, 196, 149, 253, 174, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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