← previous blocknext block →recent activity
Analyzing
Block #101,301,153
30 transactions · 27 stateful · 2026-09-02 10:11:40 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.6
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,301,153 · 30 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
1w02w03w14w08w19w010w111w212w313w415w516w620w721w822w923w224w325w428w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5095cb33…2491
0xa6afd3…d132
6 touches
3 conflicts
0x8488f10f…9354
0x34ae4d…3fc5
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity