← previous blocknext block →recent activity
Analyzing
Block #107,849,282
25 transactions · 23 stateful · 2026-09-25 08:48:16 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,849,282 · 25 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
1w02w13w24w35w410w012w013w114w215w316w417w518w619w720w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
16 touches
28 conflicts
0x28d74b23…f334
0x34b655…2a6f
14 touches
21 conflicts
0x8d5fc820…1750
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x3af0dd8e…0028
0x1b6862…e19c
10 touches
10 conflicts
0x971696fe…e1dd
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xecff7c3510…111b43
Audit this contract →
← previous block·next block →recent activity