Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26f579813bf568f6d62587d2c46c013fb657b02ead06406be163a614a096c79

Tx prefix hash: 50b67d95dc5195bd9d3ffed61a57f5911d3cdfdf1969166c954cd8c242079295
Tx public key: bdf58d4fd3b7fe27f17c6f40445c53c82166a2886a950699d24b8fc96c2ad201
Timestamp: 1737314607 Timestamp [UCT]: 2025-01-19 19:23:27 Age [y:d:h:m:s]: 00:305:03:03:53
Block: 1200934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215596 RingCT/type: yes/0
Extra: 01bdf58d4fd3b7fe27f17c6f40445c53c82166a2886a950699d24b8fc96c2ad2010211000000151f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27716bb417ec1e5323620a6b41a7f1660795874558c8e1c8cf41a53e14485a7f 0.600000000000 1687581 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": 1200944, "vin": [ { "gen": { "height": 1200934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27716bb417ec1e5323620a6b41a7f1660795874558c8e1c8cf41a53e14485a7f" } } ], "extra": [ 1, 189, 245, 141, 79, 211, 183, 254, 39, 241, 124, 111, 64, 68, 92, 83, 200, 33, 102, 162, 136, 106, 149, 6, 153, 210, 75, 143, 201, 108, 42, 210, 1, 2, 17, 0, 0, 0, 21, 31, 10, 83, 235, 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