← previous blocknext block →recent activity
Analyzing
Block #101,502,506
18 transactions · 16 stateful · 2026-09-03 03:04:51 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,502,506 · 18 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
1w02w13w24w210w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1faad01b…7acf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3dc5798b…5c87
0x34b655…2a6f
6 touches
3 conflicts
0xf9d7a5ab…d418
0x34b655…2a6f
4 touches
1 conflict
0x24bb46f7…3853
0x34b655…2a6f
4 touches
1 conflict
0x36f1d412…c60d
0x34b655…2a6f
4 touches
1 conflict
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
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 0x1faad01b5a…347acf
Audit this contract →
← previous block·next block →recent activity