← previous blocknext block →recent activity
Analyzing
Block #99,249,269
9 transactions · 9 stateful · 2026-08-26 05:47:28 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,249,269 · 9 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
1w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cc7d2e3…c1af
0x34b655…2a6f
4 touches
1 conflict
0xea79e6d3…68ad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc8a0bdc9…12e6
0x34b655…2a6f
4 touches
1 conflict
0x20d08329…c16a
0x34b655…2a6f
2 touches
0 conflicts
0x626ae3ab…68cd
0x34b655…2a6f
2 touches
0 conflicts
0x62910921…3016
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
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 0x2cc7d2e365…a9c1af
Audit this contract →
← previous block·next block →recent activity