← previous blocknext block →recent activity
Analyzing
Block #100,811,311
13 transactions · 13 stateful · 2026-08-31 17:06:52 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,811,311 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf509273e…51d3
0x851145…3f07
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0x03cabc68…bc3b
0x34b655…2a6f
2 touches
0 conflicts
0x2a22e5c9…4a64
0x34b655…2a6f
2 touches
0 conflicts
0x330587fd…4cd7
0x34b655…2a6f
2 touches
0 conflicts
0x3861b165…8482
0x34b655…2a6f
2 touches
0 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: 0x851145ea…9f3f07
10 conflicts on slot 0xf509273e1a…4a51d3
Audit this contract →
← previous block·next block →recent activity