← previous blocknext block →recent activity
Analyzing
Block #87,307,417
10 transactions · 9 stateful · 2026-07-12 16:42:58 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,307,417 · 10 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
2w03w14w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x03c2acba…6f0e
0x34b655…2a6f
2 touches
0 conflicts
0x03c2acba…6f0f
0x34b655…2a6f
2 touches
0 conflicts
0x0f6666e6…f280
0x34b655…2a6f
2 touches
0 conflicts
0x167f697f…7f61
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity