← previous blocknext block →recent activity
Analyzing
Block #87,643,804
22 transactions · 20 stateful · 2026-07-14 06:13:21 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,643,804 · 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
4w05w16w07w28w313w414w515w619w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4a7ac3…021c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x6280c6c6…11ac
0x34b655…2a6f
8 touches
6 conflicts
0x96efe05d…5d48
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7840c762…8060
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
10 conflicts on slot 0x4f4a7ac3d9…4c021c
Audit this contract →
← previous block·next block →recent activity