Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8013e55b3b4d1c9fbb23d0751f87cd18ee82d3099d0068cb0aa3a8f94c6f9265

Tx prefix hash: 63e8b9266e829129211894fe1956c9f5a65b5c89b881802c2e49090a3c79c622
Tx public key: 3fe5447580156fe62c2e0651540d7efd07a340a1d3095df18d46a40d0e260fed
Timestamp: 1729030105 Timestamp [UCT]: 2024-10-15 22:08:25 Age [y:d:h:m:s]: 00:195:11:04:34
Block: 1132434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139487 RingCT/type: yes/0
Extra: 013fe5447580156fe62c2e0651540d7efd07a340a1d3095df18d46a40d0e260fed0211000000043cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d186a79df42a857afbc99fc77a280b9c83ea24c4a465c9eb28c240e50827fbf8 0.600000000000 1615349 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": 1132444, "vin": [ { "gen": { "height": 1132434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d186a79df42a857afbc99fc77a280b9c83ea24c4a465c9eb28c240e50827fbf8" } } ], "extra": [ 1, 63, 229, 68, 117, 128, 21, 111, 230, 44, 46, 6, 81, 84, 13, 126, 253, 7, 163, 64, 161, 211, 9, 93, 241, 141, 70, 164, 13, 14, 38, 15, 237, 2, 17, 0, 0, 0, 4, 60, 208, 252, 6, 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