← previous blocknext block →recent activity
Analyzing
Block #87,716,354
22 transactions · 19 stateful · 2026-07-14 14:18:39 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,716,354 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w09w010w111w112w215w216w017w218w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc65805c2…3704
0x34b655…2a6f
6 touches
3 conflicts
0x66bc7057…c81b
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x364289f7…f98a
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
3 conflicts on slot 0xc65805c2f4…1f3704
Audit this contract →
← previous block·next block →recent activity