← previous blocknext block →recent activity
Analyzing
Block #100,791,322
31 transactions · 29 stateful · 2026-08-31 15:26:17 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,791,322 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w110w011w112w213w214w317w018w119w220w321w424w025w529w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4384fedd…c642
0x34b655…2a6f
10 touches
10 conflicts
0xfb856b8c…7557
0x34b655…2a6f
10 touches
10 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
10 touches
10 conflicts
0x9e4f30ea…3d07
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x831f75b4…945d
0x34b655…2a6f
8 touches
6 conflicts
0x641aed07…bcb9
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0x4384fedd13…e7c642
Audit this contract →
← previous block·next block →recent activity