← previous blocknext block →recent activity
Analyzing
Block #100,155,637
19 transactions · 17 stateful · 2026-08-29 10:04:03 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,155,637 · 19 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
4w08w012w113w214w115w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fe1380c…bf26
0x34b655…2a6f
8 touches
6 conflicts
0x2de59be7…3f31
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xbdb510b9…2bc4
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x1fe1380c2d…0bbf26
Audit this contract →
← previous block·next block →recent activity