← previous blocknext block →recent activity
Analyzing
Block #98,426,625
30 transactions · 22 stateful · 2026-08-23 08:05:24 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,426,625 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w012w117w019w121w223w227w228w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3b253be…78b5
0x34b655…2a6f
8 touches
6 conflicts
0xcdd556aa…31d0
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3e598447…0e3f
0xa6afd3…d132
6 touches
3 conflicts
0xf47b941b…b814
0xa6afd3…d132
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xf3b253be71…8b78b5
Audit this contract →
← previous block·next block →recent activity