← previous blocknext block →recent activity
Analyzing
Block #98,441,913
15 transactions · 14 stateful · 2026-08-23 09:22:18 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,441,913 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w08w19w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0x34b92998…c975
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity