← previous blocknext block →recent activity
Analyzing
Block #99,504,627
68 transactions · 61 stateful · 2026-08-27 03:13:02 UTC
Parallelism
94/100
Blocked
11%
Avg conflicts / tx
0.12
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,504,627 · 68 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
5w07w08w110w011w114w261w362w164w065w166w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fedc31e…37dd
0x34b655…2a6f
6 touches
3 conflicts
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4847
0x34b655…2a6f
4 touches
1 conflict
0xd9146d2f…354a
0x34b655…2a6f
4 touches
1 conflict
0xdcebb2b8…5f18
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
3 conflicts on slot 0x0fedc31e3a…4237dd
Audit this contract →
← previous block·next block →recent activity