← previous blocknext block →recent activity
Analyzing
Block #104,867,953
25 transactions · 25 stateful · 2026-09-14 22:36:59 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,867,953 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w39w410w011w115w016w117w018w119w520w622w223w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x464a82ff…41de
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xfac61869…a55f
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
10 conflicts on slot 0x464a82ff2d…8a41de
Audit this contract →
← previous block·next block →recent activity