Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 633c7689679abaaaaa19f9f134bf5f34975086ba3a9046d61f90a14347d6bf04

Tx prefix hash: 353216b6716c7b44ce6d3c11235eb725e513af7a66fa880ca975972076f4a485
Tx public key: 4b2d4a15dfde8456390e6a4a5c134ac724f3b820f6ca4c7877ee3ddeaeceb6c4
Timestamp: 1676354398 Timestamp [UCT]: 2023-02-14 05:59:58 Age [y:d:h:m:s]: 02:092:17:27:31
Block: 696601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587889 RingCT/type: yes/0
Extra: 014b2d4a15dfde8456390e6a4a5c134ac724f3b820f6ca4c7877ee3ddeaeceb6c40211000000075029cbac000000000000000000

1 output(s) for total of 3.019139223000 dcy

stealth address amount amount idx
00: 6a80ff3ddb7db8c5a0faf240ef25e14bc8ac4c9224970f2a959f152c605c9bd4 3.019139223000 1139634 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": 696611, "vin": [ { "gen": { "height": 696601 } } ], "vout": [ { "amount": 3019139223, "target": { "key": "6a80ff3ddb7db8c5a0faf240ef25e14bc8ac4c9224970f2a959f152c605c9bd4" } } ], "extra": [ 1, 75, 45, 74, 21, 223, 222, 132, 86, 57, 14, 106, 74, 92, 19, 74, 199, 36, 243, 184, 32, 246, 202, 76, 120, 119, 238, 61, 222, 174, 206, 182, 196, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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