← previous blocknext block →recent activity
Analyzing
Block #100,230,586
19 transactions · 19 stateful · 2026-08-29 16:21:20 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,230,586 · 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
1w02w13w05w06w17w28w311w212w413w517w118w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29cd05f5…390c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xeb965fed…ee71
0x34b655…2a6f
10 touches
10 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xfaafb951…950e
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
15 conflicts on slot 0x29cd05f5e7…a9390c
Audit this contract →
← previous block·next block →recent activity