Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 972db919d0855126eef33ae0616290f49b87bfa8c6e49787394b87b6330f873a

Tx prefix hash: 5d1a958c01082068055beb8dfaaee8b5b867ecfe0e5475a745011ac961460c27
Tx public key: 12b829bb2bec1fe560ed783a7b4c544a2f6f2d26af82da504d9d724c19d7b2a7
Timestamp: 1757344241 Timestamp [UCT]: 2025-09-08 15:10:41 Age [y:d:h:m:s]: 00:061:11:39:02
Block: 1364136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43934 RingCT/type: yes/0
Extra: 0112b829bb2bec1fe560ed783a7b4c544a2f6f2d26af82da504d9d724c19d7b2a702110000000cad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f842af9d5ca0a4ee477ced07b657445f8b3bc8a5f294d73428781bab4936d1 0.600000000000 1852175 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": 1364146, "vin": [ { "gen": { "height": 1364136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f842af9d5ca0a4ee477ced07b657445f8b3bc8a5f294d73428781bab4936d1" } } ], "extra": [ 1, 18, 184, 41, 187, 43, 236, 31, 229, 96, 237, 120, 58, 123, 76, 84, 74, 47, 111, 45, 38, 175, 130, 218, 80, 77, 157, 114, 76, 25, 215, 178, 167, 2, 17, 0, 0, 0, 12, 173, 121, 72, 208, 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