← previous blocknext block →recent activity
Analyzing
Block #87,662,336
17 transactions · 11 stateful · 2026-07-14 08:17:09 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,662,336 · 17 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
6w07w19w010w211w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x09385be7…8d02
0x34b655…2a6f
6 touches
3 conflicts
0x368ae947…783a
0x34b655…2a6f
6 touches
3 conflicts
0x8f825eeb…9942
0x851145…3f07
4 touches
1 conflict
0x24bef835…a52e
0x34b655…2a6f
4 touches
1 conflict
0xc15e6694…0ed1
0x34b655…2a6f
4 touches
1 conflict
0xc16295c8…b378
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity