← previous blocknext block →recent activity
Analyzing
Block #101,673,580
19 transactions · 17 stateful · 2026-09-03 17:25:28 UTC
Parallelism
47/100
Blocked
71%
Avg conflicts / tx
2.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,673,580 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w29w311w212w313w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xe2052b9a…d7cb
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0xc0a1a413…6639
0x34b655…2a6f
5 touches
3 conflicts
0xa735de1d…29b0
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity