Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ff4c2381461a1e13e1256534a415a84301ffd53ad74781ef3a266c37c63f9a1

Tx prefix hash: e60d28af816eedb4b1903d4d4ba049206416cf788668dc51b68baa46797655e1
Tx public key: 336e76d2154e9d2be6d0aabfa0897c515386500b9f3ed5e5bb82a17925b5e663
Timestamp: 1711245450 Timestamp [UCT]: 2024-03-24 01:57:30 Age [y:d:h:m:s]: 01:013:15:51:12
Block: 984996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270706 RingCT/type: yes/0
Extra: 01336e76d2154e9d2be6d0aabfa0897c515386500b9f3ed5e5bb82a17925b5e66302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5c7c53d980fa0b60befbe95c5b1554abf592287dc20c20a2eb36eb148bc0c9 0.600000000000 1445201 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": 985006, "vin": [ { "gen": { "height": 984996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5c7c53d980fa0b60befbe95c5b1554abf592287dc20c20a2eb36eb148bc0c9" } } ], "extra": [ 1, 51, 110, 118, 210, 21, 78, 157, 43, 230, 208, 170, 191, 160, 137, 124, 81, 83, 134, 80, 11, 159, 62, 213, 229, 187, 130, 161, 121, 37, 181, 230, 99, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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