← previous blocknext block →recent activity
Analyzing
Block #101,673,890
13 transactions · 13 stateful · 2026-09-03 17:27:02 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,673,890 · 13 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
1w02w13w04w15w28w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7daf6443…fd36
0x34b655…2a6f
6 touches
3 conflicts
0x898a08aa…c855
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x477cb4f5…11b4
0x34b655…2a6f
6 touches
3 conflicts
0xb3e293fe…be2e
0x34b655…2a6f
6 touches
3 conflicts
0xd17fd998…9752
0x34b655…2a6f
6 touches
3 conflicts
0xe136af8f…e687
0x34b655…2a6f
6 touches
3 conflicts
0xe6875750…9542
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
3 conflicts on slot 0x7daf644369…48fd36
Audit this contract →
← previous block·next block →recent activity