Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a0ac0c9eae40ee45b59d9fb5f5ec77b99de40afd7314a86c7e6fe5ef9660d7

Tx prefix hash: a666fadff69db4dcef882f440ffe12f3652acd080cc033977c9ee5d575c5d542
Tx public key: 7e16ba1cf4cbcfdac580b87466f5fa09c02fc2649dd3442476e8247a4af9214f
Timestamp: 1672743825 Timestamp [UCT]: 2023-01-03 11:03:45 Age [y:d:h:m:s]: 02:008:17:58:02
Block: 666639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528163 RingCT/type: yes/0
Extra: 017e16ba1cf4cbcfdac580b87466f5fa09c02fc2649dd3442476e8247a4af9214f02110000000133af99f4000000000000000000

1 output(s) for total of 3.794444633000 dcy

stealth address amount amount idx
00: ba21a61e83622b8e7b3d316172759a4af75dd472e72b1dbfa77c1c99b82f8978 3.794444633000 1107768 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": 666649, "vin": [ { "gen": { "height": 666639 } } ], "vout": [ { "amount": 3794444633, "target": { "key": "ba21a61e83622b8e7b3d316172759a4af75dd472e72b1dbfa77c1c99b82f8978" } } ], "extra": [ 1, 126, 22, 186, 28, 244, 203, 207, 218, 197, 128, 184, 116, 102, 245, 250, 9, 192, 47, 194, 100, 157, 211, 68, 36, 118, 232, 36, 122, 74, 249, 33, 79, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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