← previous blocknext block →recent activity
Analyzing
Block #102,506,164
25 transactions · 24 stateful · 2026-09-06 15:37:08 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,506,164 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w112w115w319w220w421w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x347817fd…9a4e
0x34b655…2a6f
8 touches
6 conflicts
0xa6e7f29c…5d8c
0x34b655…2a6f
6 touches
3 conflicts
0x640cb6ed…6bfd
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x18860aca…0f33
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