← previous blocknext block →recent activity
Analyzing
Block #82,293,171
14 transactions · 13 stateful · 2026-06-19 10:55:12 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,293,171 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcf827da3…f2a5
0x34b655…2a6f
6 touches
3 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
4 touches
1 conflict
0x23778a1f…dec4
0x34b655…2a6f
4 touches
1 conflict
0xec1d7176…6f5e
0x34b655…2a6f
4 touches
1 conflict
0x0462262d…a368
0x34b655…2a6f
4 touches
1 conflict
0x08913286…f0df
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity