← previous blocknext block →recent activity
Analyzing
Block #82,975,734
22 transactions · 18 stateful · 2026-06-22 14:55:02 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,975,734 · 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
1w02w13w24w05w16w27w38w49w510w311w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
12 touches
15 conflicts
0xa2dd7133…24d0
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 conflicts
0x87fd591e…94fa
0x34b655…2a6f
8 touches
6 conflicts
0xe3d06345…f84b
0x34b655…2a6f
6 touches
3 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
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
15 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity