← previous blocknext block →recent activity
Analyzing
Block #108,103,105
30 transactions · 28 stateful · 2026-09-26 06:05:47 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,103,105 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w011w112w013w115w116w217w318w421w124w025w226w328w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x588380ee…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xcc862849…98dc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0x0fb20484…1982
0x34b655…2a6f
4 touches
1 conflict
0x22158ad3…0670
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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity