← previous blocknext block →recent activity
Analyzing
Block #100,135,304
13 transactions · 13 stateful · 2026-08-29 08:21:35 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,135,304 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w08w19w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e464bec…e3e7
0x8964d7…10f8
6 touches
3 conflicts
0x2e464bec…e3ea
0x8964d7…10f8
6 touches
3 conflicts
0x2e464bec…e3eb
0x8964d7…10f8
6 touches
3 conflicts
0x2e464bec…e3ed
0x8964d7…10f8
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x2e464bec…e3e6
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 0x2e464bec22…f6e3e7
Audit this contract →
← previous block·next block →recent activity