← previous blocknext block →recent activity
Analyzing
Block #100,108,218
12 transactions · 12 stateful · 2026-08-29 06:05:09 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,108,218 · 12 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
1w02w13w14w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e44ce6a…fe19
0x34b655…2a6f
10 touches
10 conflicts
0x5b6af007…0f35
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xcd26fba5…21c6
0x34b655…2a6f
6 touches
3 conflicts
0x268b8158…a04c
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 0x8e44ce6a4c…43fe19
Audit this contract →
← previous block·next block →recent activity