← previous blocknext block →recent activity
Analyzing
Block #98,067,590
17 transactions · 16 stateful · 2026-08-22 01:58:18 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,067,590 · 17 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
1w02w06w07w18w29w311w012w113w115w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c1b956d…14d3
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x2f063f2c…f799
0x34b655…2a6f
4 touches
1 conflict
0x3d717689…0608
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x554873fd…2ff4
0x34b655…2a6f
4 touches
1 conflict
0x6401ee89…0f2b
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x5c1b956d4c…d014d3
Audit this contract →
← previous block·next block →recent activity