Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7933a313c2e580af7c48d4c747806b8e649a3f5f27eac40f8a9abbde3dff433

Tx prefix hash: 9c0ede8cf8b34a69c5ad3dde1b00f70ae1507d6dc132ff17655a611189988500
Tx public key: ccab2e0568ca1f066ac6ef1152be15f318485d8341ff0a73375d7aeee42df6b2
Timestamp: 1705880375 Timestamp [UCT]: 2024-01-21 23:39:35 Age [y:d:h:m:s]: 01:055:13:16:00
Block: 940468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300818 RingCT/type: yes/0
Extra: 01ccab2e0568ca1f066ac6ef1152be15f318485d8341ff0a73375d7aeee42df6b202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e317c33a120059e7095556c211a57deb7a70098fbd8bae4729f3bf321a922e 0.600000000000 1398606 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": 940478, "vin": [ { "gen": { "height": 940468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e317c33a120059e7095556c211a57deb7a70098fbd8bae4729f3bf321a922e" } } ], "extra": [ 1, 204, 171, 46, 5, 104, 202, 31, 6, 106, 198, 239, 17, 82, 190, 21, 243, 24, 72, 93, 131, 65, 255, 10, 115, 55, 93, 122, 238, 228, 45, 246, 178, 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