← previous blocknext block →recent activity
Analyzing
Block #102,211,307
21 transactions · 21 stateful · 2026-09-05 14:43:00 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,211,307 · 21 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
3w04w15w06w17w08w19w212w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x65c77c28…1a54
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x9bff3222…a246
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity