← previous blocknext block →recent activity
Analyzing
Block #99,623,628
24 transactions · 24 stateful · 2026-08-27 13:18:50 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,623,628 · 24 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
1w03w14w05w110w011w112w213w014w116w317w118w220w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x354d79bd…2bec
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fce7a05…d778
0x34b655…2a6f
6 touches
3 conflicts
0xefc629e7…776d
0xa6afd3…d132
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
5 touches
3 conflicts
0xe604fcc5…c348
0x40c49f…2af0
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 0x354d79bdfb…792bec
Audit this contract →
← previous block·next block →recent activity