← previous blocknext block →recent activity
Analyzing
Block #101,989,798
15 transactions · 14 stateful · 2026-09-04 20:00:11 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,989,798 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4f2b9b5…8a71
0x34b655…2a6f
6 touches
3 conflicts
0x0bb33e3f…7072
0x34b655…2a6f
4 touches
1 conflict
0x538b1eb3…6708
0x34b655…2a6f
4 touches
1 conflict
0x61a11641…fef0
0x34b655…2a6f
4 touches
1 conflict
0x674ff1fe…77a8
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x7c216fca…20cb
0x34b655…2a6f
4 touches
1 conflict
0x7c3ee46f…a8f4
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 0xc4f2b9b5ba…5f8a71
Audit this contract →
← previous block·next block →recent activity