← previous blocknext block →recent activity
Analyzing
Block #98,415,181
27 transactions · 23 stateful · 2026-08-23 07:07:49 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,415,181 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w09w113w214w317w318w120w422w425w026w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a58d502…385c
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa450ad4b…c2d5
0xa6afd3…d132
4 touches
1 conflict
0x5771b06f…14ce
0x34b655…2a6f
4 touches
1 conflict
0x5b73a3a3…80e4
0x34b655…2a6f
4 touches
1 conflict
0x79ce2c35…44f4
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
10 conflicts on slot 0x2a58d5029f…32385c
Audit this contract →
← previous block·next block →recent activity