← previous blocknext block →recent activity
Analyzing
Block #87,918,298
15 transactions · 14 stateful · 2026-07-15 12:49:28 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,918,298 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w19w210w111w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0xde4f189a…c6f3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7ba216b2…eec1
0x34b655…2a6f
4 touches
1 conflict
0x7ba216b2…eec2
0x34b655…2a6f
4 touches
1 conflict
0x814f0f40…c654
0x34b655…2a6f
4 touches
1 conflict
0x82a9bde3…9bc7
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 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity