← previous blocknext block →recent activity
Analyzing
Block #102,105,324
16 transactions · 14 stateful · 2026-09-05 05:45:50 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,105,324 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w111w212w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbfcbfd4…9251
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
6 touches
3 conflicts
0xf6ac8ccd…e4e3
0x34b655…2a6f
6 touches
3 conflicts
0xada193dc…5c7e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x045532dd…4b7d
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
6 conflicts on slot 0xcbfcbfd467…be9251
Audit this contract →
← previous block·next block →recent activity