← previous blocknext block →recent activity
Analyzing
Block #99,743,137
21 transactions · 18 stateful · 2026-08-27 23:23:00 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,743,137 · 21 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
1w03w04w114w015w117w118w019w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49299fcf…c552
0x34b655…2a6f
6 touches
3 conflicts
0x7ef52470…f3ef
0x8964d7…10f8
4 touches
1 conflict
0x7ef52470…f3e9
0x8964d7…10f8
4 touches
1 conflict
0x7ef52470…f3ec
0x8964d7…10f8
4 touches
1 conflict
0x7ef52470…f3ed
0x8964d7…10f8
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity