← previous blocknext block →recent activity
Analyzing
Block #99,290,833
16 transactions · 15 stateful · 2026-08-26 09:16:38 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,290,833 · 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
1w02w15w06w18w19w210w011w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c4afb7…5c29
0x34b655…2a6f
6 touches
3 conflicts
0x20b12e82…67dc
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x554873fd…2ff4
0x34b655…2a6f
4 touches
1 conflict
0x61b623aa…1540
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 0xc6c4afb72d…9f5c29
Audit this contract →
← previous block·next block →recent activity