← previous blocknext block →recent activity
Analyzing
Block #98,386,790
11 transactions · 9 stateful · 2026-08-23 04:44:58 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,386,790 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x930b4e5a…21b2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x3dc5798b…5c87
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8c
0x34b655…2a6f
4 touches
1 conflict
0x1408a100…f721
0x34b655…2a6f
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x930b4e5a3e…5d21b2
Audit this contract →
← previous block·next block →recent activity