← previous blocknext block →recent activity
Analyzing
Block #87,643,162
19 transactions · 13 stateful · 2026-07-14 06:09:03 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,643,162 · 19 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
8w09w110w211w316w1
- 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
0x4f4a7ac3…021c
0x34b655…2a6f
6 touches
3 conflicts
0x1786f30b…6409
0x34b655…2a6f
4 touches
1 conflict
0x1849e4e1…f8b3
0x34b655…2a6f
4 touches
1 conflict
0x4e86f6b3…99b7
0x34b655…2a6f
4 touches
1 conflict
0x66059cf4…bf4d
0x34b655…2a6f
4 touches
1 conflict
0x6fca8941…b68b
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