← previous blocknext block →recent activity
Analyzing
Block #101,019,979
25 transactions · 24 stateful · 2026-09-01 10:36:47 UTC
Parallelism
72/100
Blocked
54%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,019,979 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w17w211w012w113w214w315w416w517w619w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x297de2d5…7396
0x34b655…2a6f
14 touches
21 conflicts
0x0d6ebbcf…63e8
0x34b655…2a6f
10 touches
10 conflicts
0x9ce2d7b1…37ce
0x34b655…2a6f
10 touches
10 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x80053151…f591
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
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
21 conflicts on slot 0x297de2d577…2b7396
Audit this contract →
← previous block·next block →recent activity