← previous blocknext block →recent activity
Analyzing
Block #101,798,201
12 transactions · 11 stateful · 2026-09-04 03:52:17 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,798,201 · 12 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
1w02w13w24w39w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa086cdf1…40e7
0x34b655…2a6f
6 touches
3 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
4 touches
1 conflict
0xa735de1d…29b0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdf85f8e2…bccf
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2222135b…8843
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0xa086cdf1ca…3840e7
Audit this contract →
← previous block·next block →recent activity