Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9acb35b84fb4fe19e79098121c243cae67db17dc0e0961b4ef91031cbb8a306

Tx prefix hash: e41abcc2cc6fc287573b3cfb7e5c065f52d0da9e318454c19bdc8444faf1478b
Tx public key: 43cb10a7eaac245f48b2c41093ddfb6c89d9d50baa34b0e86c382ee6a21769d7
Timestamp: 1718382180 Timestamp [UCT]: 2024-06-14 16:23:00 Age [y:d:h:m:s]: 00:191:12:02:41
Block: 1044144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137082 RingCT/type: yes/0
Extra: 0143cb10a7eaac245f48b2c41093ddfb6c89d9d50baa34b0e86c382ee6a21769d702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6e66d34bee9a7a229716a26ef436f2d466ef4a040c76d9a02da0159894634d 0.600000000000 1513375 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": 1044154, "vin": [ { "gen": { "height": 1044144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6e66d34bee9a7a229716a26ef436f2d466ef4a040c76d9a02da0159894634d" } } ], "extra": [ 1, 67, 203, 16, 167, 234, 172, 36, 95, 72, 178, 196, 16, 147, 221, 251, 108, 137, 217, 213, 11, 170, 52, 176, 232, 108, 56, 46, 230, 162, 23, 105, 215, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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