← previous blocknext block →recent activity
Analyzing
Block #99,819,696
10 transactions · 9 stateful · 2026-08-28 05:51:09 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,819,696 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xc651939e…1660
0x8964d7…10f8
4 touches
1 conflict
0xc651939e…165a
0x8964d7…10f8
4 touches
1 conflict
0xc651939e…165b
0x8964d7…10f8
4 touches
1 conflict
0xc651939e…165e
0x8964d7…10f8
4 touches
1 conflict
0xc651939e…165f
0x8964d7…10f8
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
3 conflicts on slot 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity