← previous blocknext block →recent activity
Analyzing
Block #101,018,771
22 transactions · 18 stateful · 2026-09-01 10:30:42 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,018,771 · 22 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
1w02w19w110w214w315w416w317w418w520w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x29cd05f5…390c
0x34b655…2a6f
10 touches
10 conflicts
0x432f5f15…f1a0
0x34b655…2a6f
8 touches
6 conflicts
0xe82f7c95…8998
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0xfbde3c84…c97c
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity