← previous blocknext block →recent activity
Analyzing
Block #108,960,851
26 transactions · 22 stateful · 2026-09-29 06:07:31 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,960,851 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w110w011w015w117w118w219w320w421w522w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xab2a87f1…eb01
0x1b6862…e19c
10 touches
10 conflicts
0xb43ff748…d2ca
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0x00000000…0009
0x125f12…a50b
8 touches
6 conflicts
0x493b5af6…f877
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity