← previous blocknext block →recent activity
Analyzing
Block #104,202,589
23 transactions · 22 stateful · 2026-09-12 14:24:37 UTC
Parallelism
74/100
Blocked
45%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,202,589 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w07w19w010w113w014w115w216w317w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6060c428…7ea0
0x34b655…2a6f
10 touches
10 conflicts
0xb42efa35…7741
0x34b655…2a6f
8 touches
6 conflicts
0x27754bd4…96ae
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x485d2778…aa60
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x13db5960…6704
0x34b655…2a6f
6 touches
3 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 0x6060c4289d…d67ea0
Audit this contract →
← previous block·next block →recent activity