Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7577e1e111f7095f9ec9a682c4a50a73cf746fb8503832f767d3beca24332860

Tx prefix hash: d265d2e92ca22f4d161cafae516d0c2d6ac48d6e1b5591cf56fc1844828b89aa
Tx public key: 5e670c62720e87dd84720470e57422d75f83e313a15e6e481ff2c7d1fe3b1768
Timestamp: 1733334958 Timestamp [UCT]: 2024-12-04 17:55:58 Age [y:d:h:m:s]: 00:105:16:46:45
Block: 1168011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75360 RingCT/type: yes/0
Extra: 015e670c62720e87dd84720470e57422d75f83e313a15e6e481ff2c7d1fe3b17680211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96165e3d5d939aca6c26674956a68e626ed8517c353d31e0af1a0a047ea01eae 0.600000000000 1653718 of 15

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": 1168021, "vin": [ { "gen": { "height": 1168011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96165e3d5d939aca6c26674956a68e626ed8517c353d31e0af1a0a047ea01eae" } } ], "extra": [ 1, 94, 103, 12, 98, 114, 14, 135, 221, 132, 114, 4, 112, 229, 116, 34, 215, 95, 131, 227, 19, 161, 94, 110, 72, 31, 242, 199, 209, 254, 59, 23, 104, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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