← previous blocknext block →recent activity
Analyzing
Block #87,325,336
11 transactions · 9 stateful · 2026-07-12 18:42:51 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,325,336 · 11 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
1w03w04w15w29w3
- 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
0xbc94dfe1…0b3d
0x34b655…2a6f
6 touches
3 conflicts
0x3ef0952c…762d
0x34b655…2a6f
6 touches
3 conflicts
0xea3b49a7…24d7
0x34b655…2a6f
6 touches
3 conflicts
0x5deb3c2b…9d45
0x34b655…2a6f
4 touches
1 conflict
0x5deb3c2b…9d46
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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