← previous blocknext block →recent activity
Analyzing
Block #100,235,290
23 transactions · 21 stateful · 2026-08-29 16:45:00 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,235,290 · 23 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
1w02w13w24w36w39w010w111w413w516w617w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d17ba18…e2f1
0x34b655…2a6f
10 touches
10 conflicts
0x8db32935…81a7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x3af0dd8e…0028
0x1b6862…e19c
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
10 conflicts on slot 0x1d17ba18f4…64e2f1
Audit this contract →
← previous block·next block →recent activity