Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fe445c725e9511ba7d9fda87a0e9f9ebc4048f9769c96f42561f92f438bce55

Tx prefix hash: 0e9c2352f379e86fa0f922d91440002393dc53d3c35e588c988a68f8998b2521
Tx public key: caf5c5c4712c37e8b4d4b4aa5d900f4ed6ffddcc742deb59ff01bb206987b696
Timestamp: 1696155963 Timestamp [UCT]: 2023-10-01 10:26:03 Age [y:d:h:m:s]: 01:187:21:39:59
Block: 860081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395349 RingCT/type: yes/0
Extra: 01caf5c5c4712c37e8b4d4b4aa5d900f4ed6ffddcc742deb59ff01bb206987b69602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.867350538000 dcy

stealth address amount amount idx
00: 1be1149163e28a88fe3a201c2c0ee758da1c116eb346fd17582902a50a6a5473 0.867350538000 1314343 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": 860091, "vin": [ { "gen": { "height": 860081 } } ], "vout": [ { "amount": 867350538, "target": { "key": "1be1149163e28a88fe3a201c2c0ee758da1c116eb346fd17582902a50a6a5473" } } ], "extra": [ 1, 202, 245, 197, 196, 113, 44, 55, 232, 180, 212, 180, 170, 93, 144, 15, 78, 214, 255, 221, 204, 116, 45, 235, 89, 255, 1, 187, 32, 105, 135, 182, 150, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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