← previous blocknext block →recent activity
Analyzing
Block #100,233,410
14 transactions · 13 stateful · 2026-08-29 16:35:32 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,233,410 · 14 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
5w06w07w18w211w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf782c855…0d36
0x8964d7…10f8
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x3201a933…f586
0x8964d7…10f8
6 touches
3 conflicts
0x3201a933…f587
0x8964d7…10f8
6 touches
3 conflicts
0x3201a933…f589
0x8964d7…10f8
6 touches
3 conflicts
0xf782c855…0d30
0x8964d7…10f8
6 touches
3 conflicts
0xf782c855…0d31
0x8964d7…10f8
6 touches
3 conflicts
0xf782c855…0d34
0x8964d7…10f8
6 touches
3 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: 0x8964d7c9…5b10f8
3 conflicts on slot 0xf782c855cb…460d36
Audit this contract →
← previous block·next block →recent activity