← previous blocknext block →recent activity
Analyzing
Block #99,199,321
22 transactions · 17 stateful · 2026-08-26 01:36:10 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,199,321 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
14w015w117w218w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x9d22c394…c125
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x23255d8b…c5fd
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x605e358e…dc99
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xaab952c9…d8c9
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity