Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c5d0297754eadb97509973ea7befa718d334d15ae1b73367871a8b804ae1853

Tx prefix hash: 919cfc5a198e3bd17cc3d24089096d9a6c29f14a83a42bf79279a405857d9958
Tx public key: e5d70bdaf54520fe9a25f0332b0c64e48bc3e6377651a71b1ccdc21d429fb43a
Timestamp: 1756178096 Timestamp [UCT]: 2025-08-26 03:14:56 Age [y:d:h:m:s]: 00:135:16:36:13
Block: 1354563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96992 RingCT/type: yes/0
Extra: 01e5d70bdaf54520fe9a25f0332b0c64e48bc3e6377651a71b1ccdc21d429fb43a0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51777efaea33769a43c67516dd9f24f660159bfc85cdef86b5dc26f160a2f283 0.600000000000 1842552 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": 1354573, "vin": [ { "gen": { "height": 1354563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51777efaea33769a43c67516dd9f24f660159bfc85cdef86b5dc26f160a2f283" } } ], "extra": [ 1, 229, 215, 11, 218, 245, 69, 32, 254, 154, 37, 240, 51, 43, 12, 100, 228, 139, 195, 230, 55, 118, 81, 167, 27, 28, 205, 194, 29, 66, 159, 180, 58, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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