← previous blocknext block →recent activity
Analyzing
Block #87,418,767
14 transactions · 13 stateful · 2026-07-13 05:07:43 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,418,767 · 14 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
1w02w16w28w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x1c8b4f85…d07d
0x34b655…2a6f
4 touches
1 conflict
0x650f4caf…2abd
0x34b655…2a6f
4 touches
1 conflict
0x71fae245…1187
0x34b655…2a6f
4 touches
1 conflict
0x80d5db9f…a3fd
0x34b655…2a6f
4 touches
1 conflict
0x8267c568…f04e
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity