Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c0bc145c4f800f072f5a6602c8b8e6380a11cd88222ed4c002243104b2d0324

Tx prefix hash: 35d681c1782e15dd4f191ff5d6f06af75ea1372be4dfde86ccf84eacc53d8263
Tx public key: b4bbc90d3c49ff9c4776aec1857998e667f5e9edd67ba0db53ebe90b7ae0ad3a
Timestamp: 1700289432 Timestamp [UCT]: 2023-11-18 06:37:12 Age [y:d:h:m:s]: 02:007:12:15:35
Block: 894143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525155 RingCT/type: yes/0
Extra: 01b4bbc90d3c49ff9c4776aec1857998e667f5e9edd67ba0db53ebe90b7ae0ad3a0211000000014b8f5122000000000000000000

1 output(s) for total of 0.668856661000 dcy

stealth address amount amount idx
00: feb198467cf2513a398fb05b34b0c315488114290703452ef140891d38ac4d9b 0.668856661000 1350334 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": 894153, "vin": [ { "gen": { "height": 894143 } } ], "vout": [ { "amount": 668856661, "target": { "key": "feb198467cf2513a398fb05b34b0c315488114290703452ef140891d38ac4d9b" } } ], "extra": [ 1, 180, 187, 201, 13, 60, 73, 255, 156, 71, 118, 174, 193, 133, 121, 152, 230, 103, 245, 233, 237, 214, 123, 160, 219, 83, 235, 233, 11, 122, 224, 173, 58, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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