← previous blocknext block →recent activity
Analyzing
Block #98,431,362
15 transactions · 13 stateful · 2026-08-23 08:29:14 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,431,362 · 15 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
1w02w14w25w07w29w110w311w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a58d502…385c
0x34b655…2a6f
6 touches
3 conflicts
0x640c4fb2…044a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3e83eada…8f4c
0xd32edf…ff58
5 touches
3 conflicts
0x4979282b…2934
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x2a58d5029f…32385c
Audit this contract →
← previous block·next block →recent activity