← previous blocknext block →recent activity
Analyzing
Block #98,424,508
33 transactions · 30 stateful · 2026-08-23 07:54:45 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,424,508 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w29w010w111w215w316w318w422w324w425w430w431w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6ab090fa…d473
0xd32edf…ff58
9 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xded7601f…658c
0x065c9d…c394
7 touches
6 conflicts
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity