← previous blocknext block →recent activity
Analyzing
Block #100,783,911
47 transactions · 36 stateful · 2026-08-31 14:48:58 UTC
Parallelism
68/100
Blocked
75%
Avg conflicts / tx
1.89
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #100,783,911 · 47 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w38w09w113w114w215w318w219w421w222w326w427w529w230w132w633w234w139w741w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x81716ce9…095f
0x34b655…2a6f
12 touches
15 conflicts
0xac389ba9…8b45
0x34b655…2a6f
12 touches
15 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
8 touches
6 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
8 touches
6 conflicts
0x980c7865…00a7
0x34b655…2a6f
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity