← previous blocknext block →recent activity
Analyzing
Block #99,491,538
20 transactions · 17 stateful · 2026-08-27 02:07:09 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,491,538 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w010w111w012w214w315w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x703727d4…b1c0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xfe887199…37b3
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
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
3 conflicts on slot 0x703727d48e…53b1c0
Audit this contract →
← previous block·next block →recent activity