← previous blocknext block →recent activity
Analyzing
Block #100,787,729
35 transactions · 33 stateful · 2026-08-31 15:08:11 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,787,729 · 35 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
1w03w04w16w07w18w09w114w115w220w121w022w228w332w333w434w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
0x587be837…f33c
0x34b655…2a6f
4 touches
1 conflict
0x8cfa9962…2675
0x34b655…2a6f
4 touches
1 conflict
0xac389ba9…8b45
0x34b655…2a6f
4 touches
1 conflict
0xb20094ed…0fef
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity