← previous blocknext block →recent activity
Analyzing
Block #83,453,169
22 transactions · 18 stateful · 2026-06-24 20:06:28 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,453,169 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w18w09w110w211w312w413w514w616w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
10 touches
10 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
10 touches
10 conflicts
0xe6950848…9ff6
0x34b655…2a6f
10 touches
10 conflicts
0x872e51c8…ae2c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity