Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba81e34ae8768bd69c6be470ea31a8789ad441edbae403b76c2cf3d9bdad5a17

Tx prefix hash: ef0d620d0ec5356b7749338dde72b1487f3dd09be1f8efb5c0fa37c6190e39b7
Tx public key: f8c21c294f0fff1fe11c96c0930bc4211391875c388b077a10e33a2b006223ca
Timestamp: 1738352660 Timestamp [UCT]: 2025-01-31 19:44:20 Age [y:d:h:m:s]: 00:361:23:19:42
Block: 1209286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256375 RingCT/type: yes/0
Extra: 01f8c21c294f0fff1fe11c96c0930bc4211391875c388b077a10e33a2b006223ca021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31d232bed849db310e1e87245995b4814a792a1018df1d7e1e15f5c25dca043d 0.600000000000 1696027 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": 1209296, "vin": [ { "gen": { "height": 1209286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31d232bed849db310e1e87245995b4814a792a1018df1d7e1e15f5c25dca043d" } } ], "extra": [ 1, 248, 194, 28, 41, 79, 15, 255, 31, 225, 28, 150, 192, 147, 11, 196, 33, 19, 145, 135, 92, 56, 139, 7, 122, 16, 227, 58, 43, 0, 98, 35, 202, 2, 17, 0, 0, 0, 6, 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