← previous blocknext block →recent activity
Analyzing
Block #101,925,810
17 transactions · 17 stateful · 2026-09-04 14:35:36 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,925,810 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w37w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61ca7e1c…6d7b
0x34b655…2a6f
6 touches
3 conflicts
0x94771c29…a062
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe3a4bca8…9120
0x34b655…2a6f
6 touches
3 conflicts
0xf4e1756d…1f63
0x34b655…2a6f
6 touches
3 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x4cf69174…279d
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 0x61ca7e1cab…116d7b
Audit this contract →
← previous block·next block →recent activity