← previous blocknext block →recent activity
Analyzing
Block #99,307,741
33 transactions · 25 stateful · 2026-08-26 10:41:41 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,307,741 · 33 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
1w02w05w18w011w012w113w014w216w120w223w325w426w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x8b2b7213…4899
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x1dd7e6b1…e70f
0x34b655…2a6f
4 touches
1 conflict
0x233dd483…c152
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity