← previous blocknext block →recent activity
Analyzing
Block #108,641,020
16 transactions · 16 stateful · 2026-09-28 03:13:28 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,641,020 · 16 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
1w02w15w06w19w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68f7aaba…88df
0x34b655…2a6f
6 touches
3 conflicts
0xd0a32fa8…af82
0x34b655…2a6f
6 touches
3 conflicts
0xfc4c9ebb…ead5
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3b8da5cc…e045
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xb6039eff…b0d1
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
3 conflicts on slot 0x68f7aaba1c…9088df
Audit this contract →
← previous block·next block →recent activity