← previous blocknext block →recent activity
Analyzing
Block #87,419,246
11 transactions · 8 stateful · 2026-07-13 05:10:55 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,419,246 · 11 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x6e27bdfb…108a
0x34b655…2a6f
8 touches
6 conflicts
0x17f7e142…085e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfc4d32c0…39f9
0x34b655…2a6f
4 touches
1 conflict
0x105d58af…dec2
0x34b655…2a6f
4 touches
1 conflict
0x2ae834f7…a036
0x34b655…2a6f
4 touches
1 conflict
0x6030bece…bf0e
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