← previous blocknext block →recent activity
Analyzing
Block #100,155,601
21 transactions · 21 stateful · 2026-08-29 10:03:52 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,155,601 · 21 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
4w05w16w27w39w410w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b89cd8…5092
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x27a0c553…39a4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x1fe1380c…bf26
0x34b655…2a6f
8 touches
6 conflicts
0xf9874e36…beed
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
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 0x35b89cd80c…f05092
Audit this contract →
← previous block·next block →recent activity