← previous blocknext block →recent activity
Analyzing
Block #101,971,026
8 transactions · 7 stateful · 2026-09-04 18:24:56 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,971,026 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45082691…dff7
0x34b655…2a6f
6 touches
3 conflicts
0x3a51b0bc…7a2b
0x34b655…2a6f
6 touches
3 conflicts
0x87922600…0ec2
0x34b655…2a6f
6 touches
3 conflicts
0x0bd3f941…48ff
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
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 0x4508269153…fadff7
Audit this contract →
← previous block·next block →recent activity