← previous blocknext block →recent activity
Analyzing
Block #98,332,622
12 transactions · 12 stateful · 2026-08-23 00:12:28 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,332,622 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6828beea…cdc0
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0xfda63307…82af
0x34b655…2a6f
4 touches
1 conflict
0x1534c055…6610
0x34b655…2a6f
2 touches
0 conflicts
0x37f2cfb8…c0bb
0x34b655…2a6f
2 touches
0 conflicts
0x50e0c0f4…b772
0x34b655…2a6f
2 touches
0 conflicts
0x522acad4…5db3
0x34b655…2a6f
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 0x6828beea45…8ccdc0
Audit this contract →
← previous block·next block →recent activity