← previous blocknext block →recent activity
Analyzing
Block #101,993,536
17 transactions · 17 stateful · 2026-09-04 20:19:11 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,993,536 · 17 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
2w03w110w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
14 touches
21 conflicts
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0x7dd96c96…7335
0x34b655…2a6f
12 touches
15 conflicts
0xe93bce4c…dae1
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0xf845b6ce…0547
0x34b655…2a6f
6 touches
3 conflicts
0x93aaefce…5be5
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity