← previous blocknext block →recent activity
Analyzing
Block #89,856,203
15 transactions · 12 stateful · 2026-07-24 07:22:33 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,856,203 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w29w310w411w513w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe86a5f5…87b5
0x0a2fbf…29b1
12 touches
15 conflicts
0x1bff683e…7ecb
0x754704…b603
12 touches
15 conflicts
0x55b4e430…44cb
0x754704…b603
12 touches
15 conflicts
0x00000000…0005
0x370e2e…63b4
12 touches
15 conflicts
0x00000000…0006
0x0a2fbf…29b1
12 touches
15 conflicts
0x7d146438…9bf4
0x0a2fbf…29b1
12 touches
15 conflicts
0x7d146438…9bf5
0x0a2fbf…29b1
12 touches
15 conflicts
0xbe86a5f5…87b8
0x0a2fbf…29b1
12 touches
15 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
15 conflicts on slot 0xbe86a5f589…0387b5
Audit this contract →
← previous block·next block →recent activity