Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1ab2a9d0f0b3a98798fe8939499d43f9a53ff88005c0ed3a998a36a96ee468d

Tx prefix hash: fd5338a3c9a1470165c75666e0329c277c99b5fd7404016e6ed6e75cdd22a42b
Tx public key: 4eb30f240770dcea0bd1596a9d6bfc484cccdfb3c530a3c90460d64f3c93a3a2
Timestamp: 1754951718 Timestamp [UCT]: 2025-08-11 22:35:18 Age [y:d:h:m:s]: 00:106:15:26:45
Block: 1345079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75501 RingCT/type: yes/0
Extra: 014eb30f240770dcea0bd1596a9d6bfc484cccdfb3c530a3c90460d64f3c93a3a2021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 207ea164646b7f75173ff4bf48602da5bab4fe70c06a01cbe31ecbdfe2a914e9 0.600000000000 1832968 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": 1345089, "vin": [ { "gen": { "height": 1345079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "207ea164646b7f75173ff4bf48602da5bab4fe70c06a01cbe31ecbdfe2a914e9" } } ], "extra": [ 1, 78, 179, 15, 36, 7, 112, 220, 234, 11, 209, 89, 106, 157, 107, 252, 72, 76, 204, 223, 179, 197, 48, 163, 201, 4, 96, 214, 79, 60, 147, 163, 162, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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