← previous blocknext block →recent activity
Analyzing
Block #87,749,400
19 transactions · 18 stateful · 2026-07-14 17:59:46 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,749,400 · 19 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
1w02w16w27w09w110w211w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 conflicts
0x55b4e430…44cb
0x754704…b603
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x59152e85…50c9
0x0a2fbf…29b1
6 touches
3 conflicts
0x59152e85…50cc
0x0a2fbf…29b1
6 touches
3 conflicts
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: 0x0a2fbf2d…f729b1
10 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity