← previous blocknext block →recent activity
Analyzing
Block #99,743,862
24 transactions · 24 stateful · 2026-08-27 23:26:39 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,743,862 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w115w116w017w219w320w221w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x100ec7e6…6b5a
0x34b655…2a6f
6 touches
3 conflicts
0xb42343e0…2a28
0x34b655…2a6f
5 touches
3 conflicts
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0x0d72fcee…4b28
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity