← previous blocknext block →recent activity
Analyzing
Block #99,210,153
11 transactions · 11 stateful · 2026-08-26 02:30:39 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,210,153 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d0a36f0…174e
0x34b655…2a6f
4 touches
1 conflict
0xbd651f9a…c9ef
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x92385428…6941
0x34b655…2a6f
2 touches
0 conflicts
0xaf648aa7…39b8
0x34b655…2a6f
2 touches
0 conflicts
0xbd94f568…6ae4
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x7d0a36f069…7c174e
Audit this contract →
← previous block·next block →recent activity