← previous blocknext block →recent activity
Analyzing
Block #100,873,114
25 transactions · 21 stateful · 2026-08-31 22:17:57 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,873,114 · 25 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
1w02w03w04w17w08w110w115w217w218w319w420w121w222w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55010ec8…ea31
0x34b655…2a6f
8 touches
6 conflicts
0xf73b1957…e865
0x065c9d…c394
8 touches
6 conflicts
0xdb8f711d…201d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x86000d4b…9fbf
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
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
6 conflicts on slot 0x55010ec810…6fea31
Audit this contract →
← previous block·next block →recent activity