← previous blocknext block →recent activity
Analyzing
Block #101,988,438
20 transactions · 16 stateful · 2026-09-04 19:53:18 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,988,438 · 20 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
1w02w13w24w35w417w218w319w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf173eac8…b4ed
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x61a11641…fef0
0x34b655…2a6f
7 touches
6 conflicts
0x33761f7c…8f85
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
6 touches
3 conflicts
0x6823c28e…594c
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
6 touches
3 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 0xf173eac816…86b4ed
Audit this contract →
← previous block·next block →recent activity