← previous blocknext block →recent activity
Analyzing
Block #100,705,736
24 transactions · 22 stateful · 2026-08-31 08:15:34 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,705,736 · 24 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
1w03w06w08w112w114w015w217w118w319w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d6a99f9…da64
0x34b655…2a6f
6 touches
3 conflicts
0x14fdfaf5…4469
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x3c1c1c93…7095
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6940ae48…0c29
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
3 conflicts on slot 0x9d6a99f99b…bfda64
Audit this contract →
← previous block·next block →recent activity