← previous blocknext block →recent activity
Analyzing
Block #102,651,092
11 transactions · 11 stateful · 2026-09-07 03:50:45 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,651,092 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x06c060e1…4ff4
0x34b655…2a6f
2 touches
0 conflicts
0x0a6db9cc…cd4b
0x34b655…2a6f
2 touches
0 conflicts
0x0b0c9793…295f
0x34b655…2a6f
2 touches
0 conflicts
0x17d099d6…f79c
0x34b655…2a6f
2 touches
0 conflicts
0x2aa7be4c…0f84
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity