← previous blocknext block →recent activity
Analyzing
Block #101,661,000
24 transactions · 23 stateful · 2026-09-03 16:22:11 UTC
Parallelism
54/100
Blocked
57%
Avg conflicts / tx
1.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,661,000 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w18w09w210w312w413w514w515w616w718w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
8 touches
6 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
8 touches
6 conflicts
0xe0b7cd6d…682d
0x34b655…2a6f
8 touches
6 conflicts
0xf1a4a53d…b445
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity