Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f68bd1a27ba1c0e5b994206ef160482f301dc36fb3fa0a4c0b363155c31ae4fd

Tx prefix hash: c17d5ce1f05e184c376c7b64407fcc14e0933aa3175838ff4b362a7bf843444e
Tx public key: 6ffbf9586424117f804190c1d22ff80dd743364d68db8c216f93bfb7c06bc3a8
Timestamp: 1728580854 Timestamp [UCT]: 2024-10-10 17:20:54 Age [y:d:h:m:s]: 00:166:03:48:39
Block: 1128693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118535 RingCT/type: yes/0
Extra: 016ffbf9586424117f804190c1d22ff80dd743364d68db8c216f93bfb7c06bc3a802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e936eae9ab95862d91398994678402b6e5ca1fc12a850c403068f9c9daf47c 0.600000000000 1611514 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": 1128703, "vin": [ { "gen": { "height": 1128693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e936eae9ab95862d91398994678402b6e5ca1fc12a850c403068f9c9daf47c" } } ], "extra": [ 1, 111, 251, 249, 88, 100, 36, 17, 127, 128, 65, 144, 193, 210, 47, 248, 13, 215, 67, 54, 77, 104, 219, 140, 33, 111, 147, 191, 183, 192, 107, 195, 168, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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