← previous blocknext block →recent activity
Analyzing
Block #87,643,905
22 transactions · 18 stateful · 2026-07-14 06:14:01 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,643,905 · 22 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
2w03w15w08w09w110w211w312w215w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x96efe05d…5d48
0x34b655…2a6f
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xffb2633c…540a
0xd32edf…ff58
5 touches
3 conflicts
0x24e3bf88…17bf
0x34b655…2a6f
4 touches
1 conflict
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity