Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e65c0279c703002ca53a70af8905708af71ff3c3dde35b1abb939cd7e239b69

Tx prefix hash: 515256671ba74c61a46f2e5b4110187f4c4511a7249869e24956b789941f6495
Tx public key: 28811f2cbf24b5ca85fa790dec2a0dc3be30d2938b24532e2ee3319098c131c7
Timestamp: 1701467304 Timestamp [UCT]: 2023-12-01 21:48:24 Age [y:d:h:m:s]: 01:129:01:48:59
Block: 903899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353409 RingCT/type: yes/0
Extra: 0128811f2cbf24b5ca85fa790dec2a0dc3be30d2938b24532e2ee3319098c131c7021100000005faf35c9c000000000000000000

1 output(s) for total of 0.620879562000 dcy

stealth address amount amount idx
00: 9b76613f0aae46004c2df03a1c278535f7d2d8eeeabc675254eb9602ae66d306 0.620879562000 1360598 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": 903909, "vin": [ { "gen": { "height": 903899 } } ], "vout": [ { "amount": 620879562, "target": { "key": "9b76613f0aae46004c2df03a1c278535f7d2d8eeeabc675254eb9602ae66d306" } } ], "extra": [ 1, 40, 129, 31, 44, 191, 36, 181, 202, 133, 250, 121, 13, 236, 42, 13, 195, 190, 48, 210, 147, 139, 36, 83, 46, 46, 227, 49, 144, 152, 193, 49, 199, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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