← previous blocknext block →recent activity
Analyzing
Block #102,067,205
14 transactions · 14 stateful · 2026-09-05 02:32:23 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,067,205 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc0164b20…4db5
0x34b655…2a6f
3 touches
1 conflict
0x2b076ca1…6204
0x34b655…2a6f
3 touches
1 conflict
0x7c216fca…20cb
0x34b655…2a6f
2 touches
0 conflicts
0x897879a1…9c78
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x948836ff54…e859ab
Audit this contract →
← previous block·next block →recent activity