← previous blocknext block →recent activity
Analyzing
Block #100,230,033
19 transactions · 18 stateful · 2026-08-29 16:18:33 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,230,033 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w08w010w111w212w313w414w115w516w317w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
12 touches
15 conflicts
0x6a7e3d92…d34e
0x34b655…2a6f
6 touches
3 conflicts
0x432f5f15…f1a0
0x34b655…2a6f
6 touches
3 conflicts
0xcc5c8e3e…3d0c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity