← previous blocknext block →recent activity
Analyzing
Block #99,877,163
16 transactions · 15 stateful · 2026-08-28 10:41:25 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,877,163 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fce7a05…d778
0x34b655…2a6f
6 touches
3 conflicts
0xbe9cb1b6…6807
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x30f879d2…e39a
0x34b655…2a6f
4 touches
1 conflict
0x6eff310a…c34c
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
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
3 conflicts on slot 0x6fce7a0516…35d778
Audit this contract →
← previous block·next block →recent activity