← previous blocknext block →recent activity
Analyzing
Block #87,637,999
20 transactions · 18 stateful · 2026-07-14 05:34:37 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,637,999 · 20 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
3w04w08w09w110w011w112w213w114w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09c235f0…5a3f
0x0a2fbf…29b1
6 touches
3 conflicts
0x09c235f0…5a42
0x0a2fbf…29b1
6 touches
3 conflicts
0xd5de3f9c…0b94
0x0a2fbf…29b1
6 touches
3 conflicts
0xd5de3f9c…0b95
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0xf7b6445f…0b17
0x370e2e…63b4
6 touches
3 conflicts
0x1bff683e…7ecb
0x754704…b603
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
3 conflicts on slot 0x09c235f011…da5a3f
Audit this contract →
← previous block·next block →recent activity