← previous blocknext block →recent activity
Analyzing
Block #98,419,817
27 transactions · 24 stateful · 2026-08-23 07:31:08 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
0.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,419,817 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w08w19w210w313w015w117w118w219w420w521w123w625w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x705ab4ae…0162
0x34b655…2a6f
6 touches
3 conflicts
0x2557abf8…2901
0x34b655…2a6f
6 touches
3 conflicts
0xd4893967…d7f3
0x34b655…2a6f
6 touches
3 conflicts
0x98b8fb27…c61d
0xd32edf…ff58
5 touches
3 conflicts
0x1176d678…20ef
0x34b655…2a6f
5 touches
3 conflicts
0x9b2d3bee…8eec
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
6 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity