← previous blocknext block →recent activity
Analyzing
Block #101,992,906
15 transactions · 14 stateful · 2026-09-04 20:16:00 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,992,906 · 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
2w03w14w28w09w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb73a5ffd…ddee
0x34b655…2a6f
6 touches
3 conflicts
0xb47d4bdd…6172
0x34b655…2a6f
6 touches
3 conflicts
0xc0f6895c…e428
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x93aaefce…5be5
0x34b655…2a6f
6 touches
3 conflicts
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
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 0xb73a5ffdfa…98ddee
Audit this contract →
← previous block·next block →recent activity