← previous blocknext block →recent activity
Analyzing
Block #100,892,213
53 transactions · 50 stateful · 2026-08-31 23:54:01 UTC
Parallelism
92/100
Blocked
14%
Avg conflicts / tx
0.34
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,892,213 · 53 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
3w04w05w011w012w114w115w216w017w018w248w349w152w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
8 touches
6 conflicts
0x792b69bf…9c47
0x34b655…2a6f
6 touches
3 conflicts
0xbbdce0f1…025a
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x6affc6cd…9b19
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
6 conflicts on slot 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity