← previous blocknext block →recent activity
Analyzing
Block #101,669,618
10 transactions · 10 stateful · 2026-09-03 17:05:33 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,669,618 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf9f50167…2cd0
0x34b655…2a6f
4 touches
1 conflict
0xfe887199…37b3
0x34b655…2a6f
3 touches
1 conflict
0x110a3804…f842
0x34b655…2a6f
2 touches
0 conflicts
0x16867f4f…0bb3
0x34b655…2a6f
2 touches
0 conflicts
0x2ba59f03…90d1
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 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity