Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3eea1f08597a518890f64a05a4c73907d3fb01c7b9c5630dc6d974eb96debde

Tx prefix hash: 9020736359ae47893bfa308c804a6bc4a06a4dbf84791c886f69d13665d116a7
Tx public key: 8687f74fe34d2fa1c6d0c4845a4a7e15f8b922739b292cf9ff29cd8f5b269330
Timestamp: 1736807638 Timestamp [UCT]: 2025-01-13 22:33:58 Age [y:d:h:m:s]: 00:155:08:29:42
Block: 1196755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110740 RingCT/type: yes/0
Extra: 018687f74fe34d2fa1c6d0c4845a4a7e15f8b922739b292cf9ff29cd8f5b269330021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dd8f8a7127a1e3c2034e4c09248a1fe5fd0498d8fa1ca3b5abd3e6ab1d9ea78 0.600000000000 1683358 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": 1196765, "vin": [ { "gen": { "height": 1196755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dd8f8a7127a1e3c2034e4c09248a1fe5fd0498d8fa1ca3b5abd3e6ab1d9ea78" } } ], "extra": [ 1, 134, 135, 247, 79, 227, 77, 47, 161, 198, 208, 196, 132, 90, 74, 126, 21, 248, 185, 34, 115, 155, 41, 44, 249, 255, 41, 205, 143, 91, 38, 147, 48, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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