← previous blocknext block →recent activity
Analyzing
Block #99,981,069
23 transactions · 21 stateful · 2026-08-28 19:25:01 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,981,069 · 23 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
5w09w115w117w218w019w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ef345ef…c927
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x143cd54f…c109
0x851145…3f07
4 touches
1 conflict
0x6676e4f3…6a9e
0x851145…3f07
4 touches
1 conflict
0x32e6354f…5f73
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
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
3 conflicts on slot 0x6ef345efaa…fbc927
Audit this contract →
← previous block·next block →recent activity