← previous blocknext block →recent activity
Analyzing
Block #102,564,468
14 transactions · 13 stateful · 2026-09-06 20:32:44 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,564,468 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w39w411w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x589e817a…df78
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x53c41998…7d52
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd0ec60a1…d246
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x51fc8795…126f
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 0x589e817abe…9adf78
Audit this contract →
← previous block·next block →recent activity