← previous blocknext block →recent activity
Analyzing
Block #99,197,182
16 transactions · 16 stateful · 2026-08-26 01:25:24 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,197,182 · 16 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
1w02w13w04w15w26w07w19w210w311w113w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b7fe709…9d99
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7a86be7d…71c6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
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 0x8b7fe70996…af9d99
Audit this contract →
← previous block·next block →recent activity