← previous blocknext block →recent activity
Analyzing
Block #87,900,430
16 transactions · 15 stateful · 2026-07-15 10:49:59 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,900,430 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w28w39w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90cdf55b…8f0f
0x0a2fbf…29b1
8 touches
6 conflicts
0x90cdf55b…8f10
0x0a2fbf…29b1
8 touches
6 conflicts
0x94bc4ddb…1751
0x0a2fbf…29b1
8 touches
6 conflicts
0x94bc4ddb…1752
0x0a2fbf…29b1
8 touches
6 conflicts
0x94bc4ddb…1755
0x0a2fbf…29b1
8 touches
6 conflicts
0x00000000…0005
0x370e2e…63b4
8 touches
6 conflicts
0x1bff683e…7ecb
0x754704…b603
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
8 touches
6 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
6 conflicts on slot 0x90cdf55be9…828f0f
Audit this contract →
← previous block·next block →recent activity