Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d766935e91bb2f2e931086be6924e422640cf5575a3cf9cc5b829f35d5d0e4

Tx prefix hash: 2928839d8c15b7b7e4e061b1354ecea5d32403b8c848abfecd910f27f8a79aa3
Tx public key: 624703e52550f3dc859c58e7d65b28577852dc8ab49b8ef911cb5a7476212241
Timestamp: 1723513717 Timestamp [UCT]: 2024-08-13 01:48:37 Age [y:d:h:m:s]: 00:308:14:14:52
Block: 1086685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220366 RingCT/type: yes/0
Extra: 01624703e52550f3dc859c58e7d65b28577852dc8ab49b8ef911cb5a747621224102110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64311c7e2edfd60408e33b1313a21566d691219026883e7da8c973c16b688306 0.600000000000 1561284 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": 1086695, "vin": [ { "gen": { "height": 1086685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64311c7e2edfd60408e33b1313a21566d691219026883e7da8c973c16b688306" } } ], "extra": [ 1, 98, 71, 3, 229, 37, 80, 243, 220, 133, 156, 88, 231, 214, 91, 40, 87, 120, 82, 220, 138, 180, 155, 142, 249, 17, 203, 90, 116, 118, 33, 34, 65, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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