← previous blocknext block →recent activity
Analyzing
Block #99,496,272
7 transactions · 7 stateful · 2026-08-27 02:30:58 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,496,272 · 7 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
1w02w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9c248bc…3518
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x29eb15d2…9ba7
0x34b655…2a6f
2 touches
0 conflicts
0x62910921…3016
0x34b655…2a6f
2 touches
0 conflicts
0x67e94bf2…51b0
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
3 conflicts on slot 0xf9c248bc24…533518
Audit this contract →
← previous block·next block →recent activity