Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1667242cfafac7cf5e9c0020aee7d0c478bdee085dbb8ed1e77ede2455d8ff04

Tx prefix hash: 73a34d077d8e9ce2a669e7f2adc3dbac8937dfd2ae117e011ba80c93cec1cfed
Tx public key: ce8f487ecd3f46b211e7ebca1317d973388f3357a035c97332fd69505581040c
Timestamp: 1687018115 Timestamp [UCT]: 2023-06-17 16:08:35 Age [y:d:h:m:s]: 01:328:02:47:12
Block: 784378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495689 RingCT/type: yes/0
Extra: 01ce8f487ecd3f46b211e7ebca1317d973388f3357a035c97332fd69505581040c021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.545361997000 dcy

stealth address amount amount idx
00: 82f226f37c4a6a19894e51608b7bb833837f930ec75d820630b2b50ce09d6200 1.545361997000 1234265 of 0

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": 784388, "vin": [ { "gen": { "height": 784378 } } ], "vout": [ { "amount": 1545361997, "target": { "key": "82f226f37c4a6a19894e51608b7bb833837f930ec75d820630b2b50ce09d6200" } } ], "extra": [ 1, 206, 143, 72, 126, 205, 63, 70, 178, 17, 231, 235, 202, 19, 23, 217, 115, 56, 143, 51, 87, 160, 53, 201, 115, 50, 253, 105, 80, 85, 129, 4, 12, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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