← previous blocknext block →recent activity
Analyzing
Block #99,201,560
38 transactions · 14 stateful · 2026-08-26 01:47:26 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,201,560 · 38 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
1w02w15w07w18w236w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2e18eb17…9586
0x34b655…2a6f
4 touches
1 conflict
0x1f5a2e2b…65f1
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…1868
0x2b46c0…1669
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 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity