Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3759fa6932bc5c7747bdf3e65bad8e1a01639b6d9eac4dab122f350d1e65f97

Tx prefix hash: daf15d4ed8d2d2af0e34817b1ee7f9ac5cb683e2ecd196300f4d6ee156d75cf6
Tx public key: 34e8058a1cbfcec3b54c747820e21c4882681f5450e8ad8223a2e0328011eecc
Timestamp: 1583538680 Timestamp [UCT]: 2020-03-06 23:51:20 Age [y:d:h:m:s]: 04:297:21:20:24
Block: 77899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107364 RingCT/type: yes/0
Extra: 0134e8058a1cbfcec3b54c747820e21c4882681f5450e8ad8223a2e0328011eecc0211000000158a2ee0d9000000000000000000

1 output(s) for total of 338.757616581000 dcy

stealth address amount amount idx
00: 7a6725d189efbe643418dc14580301632e71aec31d8f69cb155aa62c6015ff09 338.757616581000 143142 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": 77909, "vin": [ { "gen": { "height": 77899 } } ], "vout": [ { "amount": 338757616581, "target": { "key": "7a6725d189efbe643418dc14580301632e71aec31d8f69cb155aa62c6015ff09" } } ], "extra": [ 1, 52, 232, 5, 138, 28, 191, 206, 195, 181, 76, 116, 120, 32, 226, 28, 72, 130, 104, 31, 84, 80, 232, 173, 130, 35, 162, 224, 50, 128, 17, 238, 204, 2, 17, 0, 0, 0, 21, 138, 46, 224, 217, 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