Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eedd220d58cc25c45e153e96180ecf12bf1b2befe41b0a1395322adde759ff43

Tx prefix hash: 9b80741ec50fef41885e7fb01424e71afb7e4a9705f08170d7870b6a1120a56d
Tx public key: 7753dbbdfb71d41e97371fa088c71d537066005e6c473b3c15047d70b1b9b209
Timestamp: 1581234923 Timestamp [UCT]: 2020-02-09 07:55:23 Age [y:d:h:m:s]: 04:324:11:22:34
Block: 61109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124100 RingCT/type: yes/0
Extra: 017753dbbdfb71d41e97371fa088c71d537066005e6c473b3c15047d70b1b9b2090211000000044ac5aa02000000000000000000

1 output(s) for total of 385.053727706000 dcy

stealth address amount amount idx
00: dbb733572b72c4855e31f19c2471749aec1704a1d3ba5108c0c26b579407a61d 385.053727706000 112622 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": 61119, "vin": [ { "gen": { "height": 61109 } } ], "vout": [ { "amount": 385053727706, "target": { "key": "dbb733572b72c4855e31f19c2471749aec1704a1d3ba5108c0c26b579407a61d" } } ], "extra": [ 1, 119, 83, 219, 189, 251, 113, 212, 30, 151, 55, 31, 160, 136, 199, 29, 83, 112, 102, 0, 94, 108, 71, 59, 60, 21, 4, 125, 112, 177, 185, 178, 9, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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