← previous blocknext block →recent activity
Analyzing
Block #99,278,151
21 transactions · 20 stateful · 2026-08-26 08:12:50 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,278,151 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w18w29w310w412w513w616w617w720w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8c0e6f5…dda2
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0xbaf77397…e798
0x34b655…2a6f
6 touches
3 conflicts
0x68dfc6ca…56ac
0x34b655…2a6f
6 touches
3 conflicts
0x40792dd3…a7fd
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
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 0xe8c0e6f528…30dda2
Audit this contract →
← previous block·next block →recent activity