← previous blocknext block →recent activity
Analyzing
Block #102,207,997
17 transactions · 16 stateful · 2026-09-05 14:26:15 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,207,997 · 17 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
1w04w17w08w111w112w213w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb6384a3…1d19
0x34b655…2a6f
8 touches
6 conflicts
0xaa072b82…3ddd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc852b267…9d14
0x34b655…2a6f
6 touches
3 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
6 touches
3 conflicts
0x4fcf90a4…c667
0x34b655…2a6f
5 touches
3 conflicts
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 0xdb6384a3f0…4c1d19
Audit this contract →
← previous block·next block →recent activity