← previous blocknext block →recent activity
Analyzing
Block #99,859,123
19 transactions · 17 stateful · 2026-08-28 09:10:33 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,859,123 · 19 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
1w04w06w07w18w29w113w314w415w516w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56cab9e9…f7d7
0x34b655…2a6f
8 touches
6 conflicts
0xfaf5fe80…1ffc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfac61869…a55b
0x1b6862…e19c
4 touches
1 conflict
0x0eac7709…66c3
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
6 conflicts on slot 0x56cab9e96a…a1f7d7
Audit this contract →
← previous block·next block →recent activity