Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b711a7e1bd1259da22e8ea67e0a1a572bc1bdad9e65b3155fb0285e55cc7c00c

Tx prefix hash: abb444dcd4669b07849deff5287b536987060ef0fddcb1a9112bf93868b0acb3
Tx public key: 13033755ab0e2d7b1740e0c1436052d5d5a1e1ea47a3b636120f8568c6282dc2
Timestamp: 1763619818 Timestamp [UCT]: 2025-11-20 06:23:38 Age [y:d:h:m:s]: 00:044:14:13:31
Block: 1416054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31947 RingCT/type: yes/0
Extra: 0113033755ab0e2d7b1740e0c1436052d5d5a1e1ea47a3b636120f8568c6282dc2021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4397ed366910ea07d89c9c83dcad0d4955c7bd4c67170ca602f982bdfbf7778f 0.600000000000 1904573 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": 1416064, "vin": [ { "gen": { "height": 1416054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4397ed366910ea07d89c9c83dcad0d4955c7bd4c67170ca602f982bdfbf7778f" } } ], "extra": [ 1, 19, 3, 55, 85, 171, 14, 45, 123, 23, 64, 224, 193, 67, 96, 82, 213, 213, 161, 225, 234, 71, 163, 182, 54, 18, 15, 133, 104, 198, 40, 45, 194, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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