Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 809bd8ee4d9224fbfb4ca3cfb77d7b20f03e4516bd3e48744c4015909eb17cc6

Tx prefix hash: 97adde97d87398a4cdc8abe7fe13fe3b0167f3a2f45dfd610fc7c188b6e3094f
Tx public key: f3a1b9b68f53fd28569ab14a41098295c9381954582c697dd56c0ca19c50ca0c
Timestamp: 1731952518 Timestamp [UCT]: 2024-11-18 17:55:18 Age [y:d:h:m:s]: 00:140:04:01:52
Block: 1156540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99998 RingCT/type: yes/0
Extra: 01f3a1b9b68f53fd28569ab14a41098295c9381954582c697dd56c0ca19c50ca0c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 008814a4b3c4c2e5c7d4c62ab5a95e297eec395e608001add42d262e31c2a644 0.600000000000 1642163 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": 1156550, "vin": [ { "gen": { "height": 1156540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "008814a4b3c4c2e5c7d4c62ab5a95e297eec395e608001add42d262e31c2a644" } } ], "extra": [ 1, 243, 161, 185, 182, 143, 83, 253, 40, 86, 154, 177, 74, 65, 9, 130, 149, 201, 56, 25, 84, 88, 44, 105, 125, 213, 108, 12, 161, 156, 80, 202, 12, 2, 17, 0, 0, 0, 1, 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