← previous blocknext block →recent activity
Analyzing
Block #100,894,779
26 transactions · 25 stateful · 2026-09-01 00:06:56 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,894,779 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w27w09w312w013w114w216w317w418w521w322w123w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e9e299e…713c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7c68d10b…8386
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0xea2d3331…6e35
0x1b6862…e19c
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 0x1e9e299e20…f8713c
Audit this contract →
← previous block·next block →recent activity