Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39e2e10f0ec486d32f1ce8d1e9ccda7d6c4a46851dc81f300627a588cdd924fd

Tx prefix hash: 989d39b0c1d31cb496ee49109e4fca6a37d2038dd6d7fbc9cf71596e86d2e424
Tx public key: a68f2a50b16850e29cbd920ba4d387bbcd1ef2cd90a43207bf2c23004bb1a2dd
Timestamp: 1583540324 Timestamp [UCT]: 2020-03-07 00:18:44 Age [y:d:h:m:s]: 04:296:11:45:12
Block: 78005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106270 RingCT/type: yes/0
Extra: 01a68f2a50b16850e29cbd920ba4d387bbcd1ef2cd90a43207bf2c23004bb1a2dd0211000000174ac5aa02000000000000000000

1 output(s) for total of 338.483767641000 dcy

stealth address amount amount idx
00: d597d6cb5b649d06d187f668e4ffa8ff2d57ff255d2bd8a2000a6d0f2a2264e7 338.483767641000 143262 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": 78015, "vin": [ { "gen": { "height": 78005 } } ], "vout": [ { "amount": 338483767641, "target": { "key": "d597d6cb5b649d06d187f668e4ffa8ff2d57ff255d2bd8a2000a6d0f2a2264e7" } } ], "extra": [ 1, 166, 143, 42, 80, 177, 104, 80, 226, 156, 189, 146, 11, 164, 211, 135, 187, 205, 30, 242, 205, 144, 164, 50, 7, 191, 44, 35, 0, 75, 177, 162, 221, 2, 17, 0, 0, 0, 23, 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