← previous blocknext block →recent activity
Analyzing
Block #102,736,687
14 transactions · 12 stateful · 2026-09-07 11:01:24 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,736,687 · 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
1w02w15w06w18w09w210w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x1d69cd40…3a60
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x7e2562e2…035c
0x34b655…2a6f
4 touches
1 conflict
0xaf4ad4d7…98d6
0x34b655…2a6f
4 touches
1 conflict
0xb09246c2…32f5
0x34b655…2a6f
4 touches
1 conflict
0xb61c1f6f…d4fc
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
10 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity