← previous blocknext block →recent activity
Analyzing
Block #100,122,716
11 transactions · 11 stateful · 2026-08-29 07:18:11 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,122,716 · 11 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
1w02w13w24w05w16w27w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x8a3ab7c9…2839
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0x3a3e7727…36c5
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity