← previous blocknext block →recent activity
Analyzing
Block #98,670,817
21 transactions · 20 stateful · 2026-08-24 05:05:33 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,670,817 · 21 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
2w03w14w25w36w27w08w19w210w012w113w115w116w217w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xdee1e659…9750
0x40c49f…2af0
4 touches
1 conflict
0xa3ed5a09…c6d3
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity