← previous blocknext block →recent activity
Analyzing
Block #87,417,094
23 transactions · 20 stateful · 2026-07-13 04:56:32 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,417,094 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w110w212w313w416w017w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x173337fe…f0af
0x34b655…2a6f
6 touches
3 conflicts
0x76ebf9c2…e0ef
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x4a870d86…79ef
0x336ed4…c59c
6 touches
3 conflicts
0xa13535db…1162
0x34b655…2a6f
6 touches
3 conflicts
0xa9660e2b…64df
0x34b655…2a6f
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
10 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity