Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234fad893b52a946f7e66ee1869d9b662632d05a6c4f263ff37ab0ce481a4979

Tx prefix hash: 2c9c3e1f3f352a8d1acfe6f27197aa06a50966c789d514aecad26a0be32150aa
Tx public key: 2fcee0931963cee5bd38809132baf73bc4f85ea792d270a40d47e8533b0bb3d5
Timestamp: 1713962238 Timestamp [UCT]: 2024-04-24 12:37:18 Age [y:d:h:m:s]: 00:258:00:12:54
Block: 1007504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184667 RingCT/type: yes/0
Extra: 012fcee0931963cee5bd38809132baf73bc4f85ea792d270a40d47e8533b0bb3d50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8847397d2695c0718ddc96020bcb2d5d5faefc2eb40f99a0e5193709aaf5364f 0.600000000000 1468866 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": 1007514, "vin": [ { "gen": { "height": 1007504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8847397d2695c0718ddc96020bcb2d5d5faefc2eb40f99a0e5193709aaf5364f" } } ], "extra": [ 1, 47, 206, 224, 147, 25, 99, 206, 229, 189, 56, 128, 145, 50, 186, 247, 59, 196, 248, 94, 167, 146, 210, 112, 164, 13, 71, 232, 83, 59, 11, 179, 213, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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