← previous blocknext block →recent activity
Analyzing
Block #100,603,512
23 transactions · 20 stateful · 2026-08-30 23:41:21 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,603,512 · 23 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
2w03w19w210w211w212w313w316w018w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9c17729…ac91
0x34b655…2a6f
8 touches
6 conflicts
0x703b1e3d…5f5e
0x34b655…2a6f
6 touches
3 conflicts
0x2314895c…2771
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7db78f05…2895
0x34b655…2a6f
6 touches
3 conflicts
0x0f28fb99…3d2f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x01306306…659d
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 0xc9c17729ae…44ac91
Audit this contract →
← previous block·next block →recent activity