Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a5058e15283282abbe9c0a89190d12002faa62613009406f8e86f39e2c49975

Tx prefix hash: bd623bf29535ba0b624af2a4d5630231e33846404c78dbfda417508a9f2e2037
Tx public key: 2554d3cbe0ffd01867d0d7cb84c756a1ee818d0b12ab875ebc93dfad5639e9a3
Timestamp: 1722747406 Timestamp [UCT]: 2024-08-04 04:56:46 Age [y:d:h:m:s]: 00:227:15:00:20
Block: 1080330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162595 RingCT/type: yes/0
Extra: 012554d3cbe0ffd01867d0d7cb84c756a1ee818d0b12ab875ebc93dfad5639e9a302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab8cc98e12156ab610ea25ee1a594ce18d1fe20983abd7de8d5520ac54a455ed 0.600000000000 1553637 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": 1080340, "vin": [ { "gen": { "height": 1080330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab8cc98e12156ab610ea25ee1a594ce18d1fe20983abd7de8d5520ac54a455ed" } } ], "extra": [ 1, 37, 84, 211, 203, 224, 255, 208, 24, 103, 208, 215, 203, 132, 199, 86, 161, 238, 129, 141, 11, 18, 171, 135, 94, 188, 147, 223, 173, 86, 57, 233, 163, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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