← previous blocknext block →recent activity
Analyzing
Block #87,704,030
26 transactions · 22 stateful · 2026-07-14 12:56:03 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,704,030 · 26 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
5w07w18w210w013w014w015w117w223w024w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbb84f537…c9b2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x0f556856…2916
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: 0xc1ff9fef…f4b0fc
3 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity