Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61104329928d221c0a31c353282308e1ba24e9ae5652e138e1076aedebe51fdc

Tx prefix hash: 6be8f8eaf46662d6c8bfabfa28d2d85f9acf7f06dc0023d38fd38720d987931b
Tx public key: 07a338344d9d26a70c01cd074da011475d24b3b7c510055c7c3aa0f97026fc83
Timestamp: 1702034686 Timestamp [UCT]: 2023-12-08 11:24:46 Age [y:d:h:m:s]: 01:132:06:27:07
Block: 908605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355698 RingCT/type: yes/0
Extra: 0107a338344d9d26a70c01cd074da011475d24b3b7c510055c7c3aa0f97026fc8302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2954791632eba9fe6148032ad53c6dac07cddd5b3871c07fbd8dc9e50da38e9 0.600000000000 1365650 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": 908615, "vin": [ { "gen": { "height": 908605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2954791632eba9fe6148032ad53c6dac07cddd5b3871c07fbd8dc9e50da38e9" } } ], "extra": [ 1, 7, 163, 56, 52, 77, 157, 38, 167, 12, 1, 205, 7, 77, 160, 17, 71, 93, 36, 179, 183, 197, 16, 5, 92, 124, 58, 160, 249, 112, 38, 252, 131, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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