← previous blocknext block →recent activity
Analyzing
Block #98,422,479
13 transactions · 12 stateful · 2026-08-23 07:44:32 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,422,479 · 13 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
2w03w15w06w17w08w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x403a4649…d8be
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x0ce69307…e9a9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2c2db8e9…fdc7
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 0x403a46498c…f3d8be
Audit this contract →
← previous block·next block →recent activity