← previous blocknext block →recent activity
Analyzing
Block #108,610,596
25 transactions · 22 stateful · 2026-09-28 00:40:13 UTC
Parallelism
48/100
Blocked
64%
Avg conflicts / tx
2.68
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #108,610,596 · 25 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w822w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
18 touches
36 conflicts
0xc060fcda…f3a4
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0xd1480c90…ae0b
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0009
0x125f12…a50b
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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: 0x125f12a1…cda50b
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity