Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7d943a50fe4eb0083b9566c3893a798885b66229e4873c75f9fcd9ca6e5226

Tx prefix hash: ce1cbb6109a2d947499200eb99b99e2a92890a3814f3195b8bd663f2a7f55f1f
Tx public key: 2df43ac33e3421d9960827903b491f4743a542edf6d5f25ecb155bf842806c6e
Timestamp: 1583633938 Timestamp [UCT]: 2020-03-08 02:18:58 Age [y:d:h:m:s]: 05:043:08:22:25
Block: 78358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186434 RingCT/type: yes/0
Extra: 012df43ac33e3421d9960827903b491f4743a542edf6d5f25ecb155bf842806c6e0211000000015143fba2000000000000000000

1 output(s) for total of 337.573394166000 dcy

stealth address amount amount idx
00: 8976bde5ff7cf8b4209e2630d87ee2fd3aa60ae8e05ef725d79d91d3c134b2c5 337.573394166000 143802 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": 78368, "vin": [ { "gen": { "height": 78358 } } ], "vout": [ { "amount": 337573394166, "target": { "key": "8976bde5ff7cf8b4209e2630d87ee2fd3aa60ae8e05ef725d79d91d3c134b2c5" } } ], "extra": [ 1, 45, 244, 58, 195, 62, 52, 33, 217, 150, 8, 39, 144, 59, 73, 31, 71, 67, 165, 66, 237, 246, 213, 242, 94, 203, 21, 91, 248, 66, 128, 108, 110, 2, 17, 0, 0, 0, 1, 81, 67, 251, 162, 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