← previous blocknext block →recent activity
Analyzing
Block #87,749,302
16 transactions · 13 stateful · 2026-07-14 17:59:06 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,749,302 · 16 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
6w07w18w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1b6e8fc2…73d4
0x34b655…2a6f
4 touches
1 conflict
0x35cfae1b…c1f8
0x34b655…2a6f
4 touches
1 conflict
0x3f4d9d89…7299
0x34b655…2a6f
4 touches
1 conflict
0x55c2c22c…0474
0x34b655…2a6f
4 touches
1 conflict
0x7a0c1142…55df
0x34b655…2a6f
4 touches
1 conflict
0x7c6cfc14…9957
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