← previous blocknext block →recent activity
Analyzing
Block #88,075,908
14 transactions · 12 stateful · 2026-07-16 06:23:38 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,075,908 · 14 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
1w02w13w04w15w29w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf95f86cd…e927
0x34b655…2a6f
6 touches
3 conflicts
0x992fec28…420d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe84e88e5…aabf
0x34b655…2a6f
4 touches
1 conflict
0xeafb6102…13f8
0x34b655…2a6f
4 touches
1 conflict
0x0df4e383…e1ab
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 0xf95f86cd53…dfe927
Audit this contract →
← previous block·next block →recent activity