← previous blocknext block →recent activity
Analyzing
Block #99,857,627
23 transactions · 22 stateful · 2026-08-28 09:02:58 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,857,627 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w27w08w19w210w012w213w314w417w221w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc16e646d…4fb0
0x34b655…2a6f
8 touches
6 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
6 touches
3 conflicts
0x272e6316…bbe8
0x34b655…2a6f
6 touches
3 conflicts
0x3114eedf…e836
0x34b655…2a6f
6 touches
3 conflicts
0x3da4a10d…a642
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
6 conflicts on slot 0xc16e646d81…a44fb0
Audit this contract →
← previous block·next block →recent activity