← previous blocknext block →recent activity
Analyzing
Block #102,215,930
14 transactions · 13 stateful · 2026-09-05 15:06:25 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,215,930 · 14 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
1w04w06w07w18w210w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2fa90b4…0814
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0xac27d4e9…fffc
0x34b655…2a6f
3 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 0xd2fa90b4e6…440814
Audit this contract →
← previous block·next block →recent activity