← previous blocknext block →recent activity
Analyzing
Block #100,920,268
13 transactions · 10 stateful · 2026-09-01 02:15:08 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,920,268 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831f75b4…945d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x29cd05f5…390c
0x34b655…2a6f
2 touches
0 conflicts
0x42d8f3e4…4199
0x34b655…2a6f
2 touches
0 conflicts
0x4e4b3596…413b
0x34b655…2a6f
2 touches
0 conflicts
0x910e1ba1…717a
0x34b655…2a6f
2 touches
0 conflicts
0x932a9590…0b19
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x831f75b4aa…17945d
Audit this contract →
← previous block·next block →recent activity