← previous blocknext block →recent activity
Analyzing
Block #101,967,794
22 transactions · 20 stateful · 2026-09-04 18:08:35 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
2.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,967,794 · 22 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
1w02w15w17w09w110w111w212w316w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7aad02c6…b979
0x34b655…2a6f
14 touches
21 conflicts
0xc166a323…1f33
0x34b655…2a6f
9 touches
10 conflicts
0x3d408a46…8a53
0x34b655…2a6f
8 touches
6 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
7 touches
6 conflicts
0xf04da8ca…d938
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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
28 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity