← previous blocknext block →recent activity
Analyzing
Block #99,105,403
17 transactions · 17 stateful · 2026-08-25 17:43:34 UTC
Parallelism
59/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,105,403 · 17 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
1w06w07w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb0f5d668…99ac
0x34b655…2a6f
8 touches
6 conflicts
0x4761cb29…47a5
0x34b655…2a6f
4 touches
1 conflict
0x52640507…df00
0x34b655…2a6f
4 touches
1 conflict
0x6ec32a5b…83dd
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
10 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity