← previous blocknext block →recent activity
Analyzing
Block #99,163,008
11 transactions · 11 stateful · 2026-08-25 22:33:28 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,163,008 · 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
5w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xccdc32f8…72be
0x34b655…2a6f
4 touches
1 conflict
0xa53873f0…f0b3
0x34b655…2a6f
3 touches
1 conflict
0xdab6a6d4…23ba
0x34b655…2a6f
3 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
2 touches
0 conflicts
0x41d113ae…d58a
0x34b655…2a6f
2 touches
0 conflicts
0x4bfdfe91…1ec2
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity