← previous blocknext block →recent activity
Analyzing
Block #98,148,302
33 transactions · 26 stateful · 2026-08-22 08:45:08 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,148,302 · 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
4w05w06w17w210w311w416w019w026w530w131w632w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x705a9a1a…db08
0x34b655…2a6f
6 touches
3 conflicts
0x17dc154e…8f4b
0x34b655…2a6f
4 touches
1 conflict
0x18148d99…92eb
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2531b293…51c6
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity