← previous blocknext block →recent activity
Analyzing
Block #99,262,034
17 transactions · 15 stateful · 2026-08-26 06:51:46 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,262,034 · 17 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
1w02w15w08w210w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe45073e…6315
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb1277a25…706f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xce0597a3…3aa7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0xfe45073ed9…0c6315
Audit this contract →
← previous block·next block →recent activity