← previous blocknext block →recent activity
Analyzing
Block #87,663,613
31 transactions · 25 stateful · 2026-07-14 08:25:42 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,663,613 · 31 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
5w06w07w18w010w113w214w317w018w119w220w321w422w323w430w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72bc40aa…4c4b
0x0a2fbf…29b1
10 touches
10 conflicts
0x8bb57615…2a2a
0x0a2fbf…29b1
10 touches
10 conflicts
0x8bb57615…2a2b
0x0a2fbf…29b1
10 touches
10 conflicts
0x72bc40aa…4c4c
0x0a2fbf…29b1
10 touches
10 conflicts
0x00000000…0005
0x370e2e…63b4
10 touches
10 conflicts
0x1bff683e…7ecb
0x754704…b603
10 touches
10 conflicts
0x55b4e430…44cb
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x0a2fbf…29b1
10 touches
10 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 0x72bc40aafb…d04c4b
Audit this contract →
← previous block·next block →recent activity