← previous blocknext block →recent activity
Analyzing
Block #101,968,688
12 transactions · 8 stateful · 2026-09-04 18:13:07 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,968,688 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1d9f34f…7ce1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x91b13e91…855d
0x34b655…2a6f
4 touches
1 conflict
0x34b6fb88…1170
0x34b655…2a6f
2 touches
0 conflicts
0x682e1d93…b8fb
0x34b655…2a6f
2 touches
0 conflicts
0x74ba5890…79bc
0x34b655…2a6f
2 touches
0 conflicts
0x8f3c038f…528f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc1d9f34f02…697ce1
Audit this contract →
← previous block·next block →recent activity