Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d9f85102dd6a416535ab3fa55dbedaaa2ee2af18c376a31999efd89d0d8f9c

Tx prefix hash: 34c1b5f58f48ed90d337aeaa41a793f76005c383573544392054667c69e86b9e
Tx public key: 4eacc9bfa57f66e2b4744db03e4526c035df7ca8cc56f2b285e630272d327f29
Timestamp: 1734851080 Timestamp [UCT]: 2024-12-22 07:04:40 Age [y:d:h:m:s]: 00:179:17:59:12
Block: 1180583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128136 RingCT/type: yes/0
Extra: 014eacc9bfa57f66e2b4744db03e4526c035df7ca8cc56f2b285e630272d327f290211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fcde90876b2f34e0b9bec0be748fe1bc50363ff46c4215d7020032fa49bb8e8 0.600000000000 1666996 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": 1180593, "vin": [ { "gen": { "height": 1180583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fcde90876b2f34e0b9bec0be748fe1bc50363ff46c4215d7020032fa49bb8e8" } } ], "extra": [ 1, 78, 172, 201, 191, 165, 127, 102, 226, 180, 116, 77, 176, 62, 69, 38, 192, 53, 223, 124, 168, 204, 86, 242, 178, 133, 230, 48, 39, 45, 50, 127, 41, 2, 17, 0, 0, 0, 6, 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