Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2039d6fbad22e26fb7a0de9a2b94cf86c9cacb3225a178c375a07099be643ee3

Tx prefix hash: 67c8baf7a66a4898f36af46724efb47b4b7d0984c11931a9f0eea601beb7ea3b
Tx public key: d74906cb90a8bc7487059bd0c476b959b95e9770f6c2f5070f572347655d9ba3
Timestamp: 1722120358 Timestamp [UCT]: 2024-07-27 22:45:58 Age [y:d:h:m:s]: 00:287:19:36:59
Block: 1075138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205632 RingCT/type: yes/0
Extra: 01d74906cb90a8bc7487059bd0c476b959b95e9770f6c2f5070f572347655d9ba3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e8ea86af060c4a806c82a2fcbbd82cc2bfe134d9a676a6541324249f81d223d 0.600000000000 1547661 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": 1075148, "vin": [ { "gen": { "height": 1075138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e8ea86af060c4a806c82a2fcbbd82cc2bfe134d9a676a6541324249f81d223d" } } ], "extra": [ 1, 215, 73, 6, 203, 144, 168, 188, 116, 135, 5, 155, 208, 196, 118, 185, 89, 185, 94, 151, 112, 246, 194, 245, 7, 15, 87, 35, 71, 101, 93, 155, 163, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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