← previous blocknext block →recent activity
Analyzing
Block #109,143,618
28 transactions · 23 stateful · 2026-09-29 21:30:02 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,143,618 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w011w012w113w214w315w416w318w525w527w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3210155…cca4
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x083a8763…5a79
0x1b6862…e19c
8 touches
6 conflicts
0xdbda0ced…a9d9
0xd32edf…ff58
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0xd321015592…9dcca4
Audit this contract →
← previous block·next block →recent activity