← previous blocknext block →recent activity
Analyzing
Block #100,619,688
27 transactions · 26 stateful · 2026-08-31 01:02:44 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,619,688 · 27 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
1w04w06w07w18w29w010w113w014w216w317w318w122w423w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15698ac9…2a46
0x34b655…2a6f
8 touches
6 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x28aa8ed1…01e5
0x34b655…2a6f
6 touches
3 conflicts
0x52d77b92…60e3
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
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 0x15698ac9db…df2a46
Audit this contract →
← previous block·next block →recent activity