← previous blocknext block →recent activity
Analyzing
Block #104,148,549
22 transactions · 19 stateful · 2026-09-12 09:50:16 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,148,549 · 22 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
1w02w13w24w35w06w18w210w011w113w214w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a69c7c5…09cc
0x34b655…2a6f
14 touches
21 conflicts
0xe2c7ff81…8bfd
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x1408e7c7…f324
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x485d2778…aa5f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0x1a69c7c52c…7b09cc
Audit this contract →
← previous block·next block →recent activity