← previous blocknext block →recent activity
Analyzing
Block #101,060,670
37 transactions · 27 stateful · 2026-09-01 14:01:30 UTC
Parallelism
73/100
Blocked
70%
Avg conflicts / tx
1.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,060,670 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w010w311w212w313w416w417w318w419w420w521w622w723w824w931w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x330cd817…a53e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x1045386d…cb86
0x1b6862…e19c
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity