← previous blocknext block →recent activity
Analyzing
Block #82,976,344
23 transactions · 19 stateful · 2026-06-22 14:59:06 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,976,344 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w512w615w117w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0xa4e5e0c2…6e04
0x34b655…2a6f
8 touches
6 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
8 touches
6 conflicts
0x52342825…6e5c
0x34b655…2a6f
7 touches
6 conflicts
0x79d50d4a…951d
0x34b655…2a6f
6 touches
3 conflicts
0x87fd591e…94fa
0x34b655…2a6f
6 touches
3 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
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
21 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity