← previous blocknext block →recent activity
Analyzing
Block #107,277,925
58 transactions · 53 stateful · 2026-09-23 08:50:22 UTC
Parallelism
72/100
Blocked
72%
Avg conflicts / tx
2.98
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #107,277,925 · 58 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w111w312w415w116w217w318w423w227w529w633w336w837w939w442w1343w1448w649w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b2ba87…21ff
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…001c
0x1b6862…e19c
18 touches
36 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
18 touches
36 conflicts
0x4017e4a5…194a
0xd32edf…ff58
17 touches
36 conflicts
0x51087f5a…61f7
0x34b655…2a6f
16 touches
28 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x24b2ba879e…a721ff
Audit this contract →
← previous block·next block →recent activity