← previous blocknext block →recent activity
Analyzing
Block #99,308,591
17 transactions · 15 stateful · 2026-08-26 10:45:58 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,308,591 · 17 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
1w02w03w04w17w18w29w110w311w412w513w515w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b7fe709…9d99
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc74ccb86…9c85
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0x569384d9…8585
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0xaa30fe32…6191
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
15 conflicts on slot 0x8b7fe70996…af9d99
Audit this contract →
← previous block·next block →recent activity