← previous blocknext block →recent activity
Analyzing
Block #99,038,045
22 transactions · 19 stateful · 2026-08-25 12:01:06 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,038,045 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w18w110w211w212w313w115w218w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x2274142b…f885
0x851145…3f07
6 touches
3 conflicts
0xeffd747c…6a01
0x851145…3f07
6 touches
3 conflicts
0x295780b7…d2d1
0x34b655…2a6f
6 touches
3 conflicts
0x8b98c194…d69e
0x851145…3f07
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity