Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc1f643d27ebc5583fc6a4663b1eb6f521732fe178d0ca848cc050cda3068e90

Tx prefix hash: d9e78dd8c56c57c49f6cb55b1eaa800361241e8b548aea318e9d9fcfa0b7436c
Tx public key: 1a243c1fb1975554017ac0de9d7325367a05e6f5cb9c748db46bdfe93185745b
Timestamp: 1762616471 Timestamp [UCT]: 2025-11-08 15:41:11 Age [y:d:h:m:s]: 00:045:09:54:27
Block: 1407740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32511 RingCT/type: yes/0
Extra: 011a243c1fb1975554017ac0de9d7325367a05e6f5cb9c748db46bdfe93185745b021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0835e65d6f39b47ca48eb13e1f889b5ce849ef2a11b51e45bad0e1a950a17c7c 0.600000000000 1896161 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": 1407750, "vin": [ { "gen": { "height": 1407740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0835e65d6f39b47ca48eb13e1f889b5ce849ef2a11b51e45bad0e1a950a17c7c" } } ], "extra": [ 1, 26, 36, 60, 31, 177, 151, 85, 84, 1, 122, 192, 222, 157, 115, 37, 54, 122, 5, 230, 245, 203, 156, 116, 141, 180, 107, 223, 233, 49, 133, 116, 91, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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