← previous blocknext block →recent activity
Analyzing
Block #101,956,583
50 transactions · 45 stateful · 2026-09-04 17:11:45 UTC
Parallelism
58/100
Blocked
71%
Avg conflicts / tx
4.24
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #101,956,583 · 50 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w010w111w213w015w116w217w318w419w520w621w722w130w137w942w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
36 touches
153 conflicts
0xf3d10975…0d07
0x34b655…2a6f
20 touches
45 conflicts
0xea02471d…1542
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
16 touches
28 conflicts
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0x070a562a…8147
0x34b655…2a6f
9 touches
10 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
153 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity