← previous blocknext block →recent activity
Analyzing
Block #98,450,968
10 transactions · 8 stateful · 2026-08-23 10:07:52 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,450,968 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f5e33f…719c
0x34b655…2a6f
4 touches
1 conflict
0x88ecacda…04c9
0xa6afd3…d132
4 touches
1 conflict
0xa0a8ac53…199c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x7151b1ad…4520
0x34b655…2a6f
4 touches
1 conflict
0x14764922…c57d
0xa6afd3…d132
3 touches
1 conflict
0x69c8bf4a…2ed0
0x754704…b603
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 0xe8f5e33f0f…b6719c
Audit this contract →
← previous block·next block →recent activity