← previous blocknext block →recent activity
Analyzing
Block #104,811,007
42 transactions · 34 stateful · 2026-09-14 17:49:27 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,811,007 · 42 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
5w06w19w210w012w116w317w420w521w622w737w038w139w240w341w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x059e0ac0…0267
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x91913ff0…97f8
0x34b655…2a6f
8 touches
6 conflicts
0xfe2577ac…677b
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
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 0x059e0ac09d…0f0267
Audit this contract →
← previous block·next block →recent activity