← previous blocknext block →recent activity
Analyzing
Block #99,616,083
15 transactions · 11 stateful · 2026-08-27 12:40:09 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,616,083 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d114832…03a4
0x34b655…2a6f
8 touches
6 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
8 touches
6 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x4245140b…2b83
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
2 touches
0 conflicts
0x939cdd56…00c8
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 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 0x5d1148320e…6403a4
Audit this contract →
← previous block·next block →recent activity