← previous blocknext block →recent activity
Analyzing
Block #101,663,621
23 transactions · 22 stateful · 2026-09-03 16:35:22 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,663,621 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w17w28w29w210w011w313w014w117w418w519w621w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4089d428…b018
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
6 touches
3 conflicts
0x3f455b3e…9b3b
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0xb73a5ffd…ddee
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
10 conflicts on slot 0x4089d42830…afb018
Audit this contract →
← previous block·next block →recent activity