← previous blocknext block →recent activity
Analyzing
Block #87,791,638
22 transactions · 20 stateful · 2026-07-14 22:42:19 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,791,638 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w011w012w113w214w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x1445ffc7…e961
0x34b655…2a6f
4 touches
1 conflict
0x1445ffc7…e962
0x34b655…2a6f
4 touches
1 conflict
0x166fc980…8d87
0x34b655…2a6f
4 touches
1 conflict
0x3e950538…2259
0x34b655…2a6f
4 touches
1 conflict
0x6b75f0c2…d323
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity