← previous blocknext block →recent activity
Analyzing
Block #82,654,144
24 transactions · 11 stateful · 2026-06-21 03:06:19 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,654,144 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w115w220w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb624d2ea…8c87
0x34b655…2a6f
8 touches
6 conflicts
0xfcb9138a…3830
0xc8689a…ee79
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x26abe30c…f680
0x34b655…2a6f
4 touches
1 conflict
0x2ee7e7c6…b7b1
0x34b655…2a6f
4 touches
1 conflict
0x668c760a…1c1f
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
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
6 conflicts on slot 0xb624d2eae3…2b8c87
Audit this contract →
← previous block·next block →recent activity