Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08e915be49a1a03cd2a5f8a56a9d1eaab14200f4fde276726d402b45f0953b9f

Tx prefix hash: 161c3e29134ece93072ab4ba4320bdc8d9911d948878fb8c24410e5cad7c8809
Tx public key: 77f9e4945c7622b036e7ca60a18eade2d9b4e5052b2633aaacf4a59bbda71dba
Timestamp: 1716094189 Timestamp [UCT]: 2024-05-19 04:49:49 Age [y:d:h:m:s]: 00:236:22:08:48
Block: 1025175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169562 RingCT/type: yes/0
Extra: 0177f9e4945c7622b036e7ca60a18eade2d9b4e5052b2633aaacf4a59bbda71dba0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90ccf5f8bb4a5a1bbb482bf786c81ce520f2f18fe206ce44fad040540e795a69 0.600000000000 1491482 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": 1025185, "vin": [ { "gen": { "height": 1025175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90ccf5f8bb4a5a1bbb482bf786c81ce520f2f18fe206ce44fad040540e795a69" } } ], "extra": [ 1, 119, 249, 228, 148, 92, 118, 34, 176, 54, 231, 202, 96, 161, 142, 173, 226, 217, 180, 229, 5, 43, 38, 51, 170, 172, 244, 165, 155, 189, 167, 29, 186, 2, 17, 0, 0, 0, 8, 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