← previous blocknext block →recent activity
Analyzing
Block #99,442,562
22 transactions · 22 stateful · 2026-08-26 22:00:31 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,442,562 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w08w19w210w314w015w016w117w018w019w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc2de485…918d
0x34b655…2a6f
8 touches
6 conflicts
0xedb616b2…a47f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x903069bd…d212
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
6 conflicts on slot 0xbc2de48528…c6918d
Audit this contract →
← previous block·next block →recent activity