← previous blocknext block →recent activity
Analyzing
Block #101,966,222
13 transactions · 13 stateful · 2026-09-04 18:00:38 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,966,222 · 13 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
1w02w17w28w09w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e06d07b…36af
0x34b655…2a6f
6 touches
3 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
6 touches
3 conflicts
0x5efd7300…d8a5
0x34b655…2a6f
6 touches
3 conflicts
0x5157fcca…2de4
0xd32edf…ff58
5 touches
3 conflicts
0x24bd2bba…829a
0x34b655…2a6f
5 touches
3 conflicts
0x56e4f5e4…fe8a
0x34b655…2a6f
4 touches
2 conflicts
0x00000000…00c9
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity