Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2496b7254a7162eb7b4744f9b72f0cbcf4a395e836e141b0ee74e72b4a92ed36

Tx prefix hash: e0d09080631edc6a3b75a50f368a102071d5507ff0df9f5448046b922ad569e5
Tx public key: 66724f665bc246da72ebaf7f2b3f44cc577d8e3e173f975ef11436ef23d0a3e3
Timestamp: 1581472984 Timestamp [UCT]: 2020-02-12 02:03:04 Age [y:d:h:m:s]: 05:265:18:52:24
Block: 63083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1340512 RingCT/type: yes/0
Extra: 0166724f665bc246da72ebaf7f2b3f44cc577d8e3e173f975ef11436ef23d0a3e30211000000054943cd9f000000000000000000

1 output(s) for total of 379.298083054000 dcy

stealth address amount amount idx
00: e886efa1170ec602181ff99b5a840fb7321286badf766098773ee20120c62d9c 379.298083054000 116347 of 0

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": 63093, "vin": [ { "gen": { "height": 63083 } } ], "vout": [ { "amount": 379298083054, "target": { "key": "e886efa1170ec602181ff99b5a840fb7321286badf766098773ee20120c62d9c" } } ], "extra": [ 1, 102, 114, 79, 102, 91, 194, 70, 218, 114, 235, 175, 127, 43, 63, 68, 204, 87, 125, 142, 62, 23, 63, 151, 94, 241, 20, 54, 239, 35, 208, 163, 227, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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