Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8eab57957f4a7a47ae38ba16c51ab73ab19654821f1a10310cd605fe1384c77

Tx prefix hash: 025274ee3ff464654d9598c60c2b580c607a2d0b999aa527487644fa09e92bf6
Tx public key: a43e79a61edb0ba77c34c731ad7f02d0aa37ae00321f04d85600f968dc9f0fcb
Timestamp: 1719182965 Timestamp [UCT]: 2024-06-23 22:49:25 Age [y:d:h:m:s]: 00:283:21:48:20
Block: 1050771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202877 RingCT/type: yes/0
Extra: 01a43e79a61edb0ba77c34c731ad7f02d0aa37ae00321f04d85600f968dc9f0fcb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b02137dc87bae5667d781cec0a75d6c810326ab8e450f7b5ada972fa40dd60ef 0.600000000000 1520946 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": 1050781, "vin": [ { "gen": { "height": 1050771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b02137dc87bae5667d781cec0a75d6c810326ab8e450f7b5ada972fa40dd60ef" } } ], "extra": [ 1, 164, 62, 121, 166, 30, 219, 11, 167, 124, 52, 199, 49, 173, 127, 2, 208, 170, 55, 174, 0, 50, 31, 4, 216, 86, 0, 249, 104, 220, 159, 15, 203, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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