Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b6e85a409340b55c7e59da2eaff21e67412c37bfe46acbe8a3f570adc1fab0

Tx prefix hash: 5d7f7456c205768d68edb82707053e0df408026d5f87e014c8ee8d2bc9796cf7
Tx public key: 1e672cdc6a0ee6cddfdcdd33366cf25e2366ba4ad345ed1689cb88a68e34e6a1
Timestamp: 1744852229 Timestamp [UCT]: 2025-04-17 01:10:29 Age [y:d:h:m:s]: 00:211:20:09:36
Block: 1263083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149127 RingCT/type: yes/0
Extra: 011e672cdc6a0ee6cddfdcdd33366cf25e2366ba4ad345ed1689cb88a68e34e6a1021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 512a1b1d3baf51308626bfe31420d03239818fc7b84b53a4b89405544526c602 0.600000000000 1750266 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": 1263093, "vin": [ { "gen": { "height": 1263083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "512a1b1d3baf51308626bfe31420d03239818fc7b84b53a4b89405544526c602" } } ], "extra": [ 1, 30, 103, 44, 220, 106, 14, 230, 205, 223, 220, 221, 51, 54, 108, 242, 94, 35, 102, 186, 74, 211, 69, 237, 22, 137, 203, 136, 166, 142, 52, 230, 161, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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