← previous blocknext block →recent activity
Analyzing
Block #100,082,896
27 transactions · 21 stateful · 2026-08-29 03:57:40 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,082,896 · 27 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
1w04w15w06w09w010w111w212w316w418w522w623w224w326w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x627738d1…db02
0x34b655…2a6f
14 touches
21 conflicts
0x6415c9bf…6c16
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0xe4af4c87…9964
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x73b5ba07…3d3a
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x627738d150…b6db02
Audit this contract →
← previous block·next block →recent activity