← previous blocknext block →recent activity
Analyzing
Block #108,972,124
36 transactions · 30 stateful · 2026-09-29 07:04:43 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.81
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #108,972,124 · 36 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w59w611w712w822w235w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xc12eeaad…8f7d
0xd32edf…ff58
17 touches
36 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0040
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0057
0x1b6862…e19c
14 touches
21 conflicts
0x0e64cf42…c998
0x1b6862…e19c
14 touches
21 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity