← previous blocknext block →recent activity
Analyzing
Block #104,023,768
16 transactions · 16 stateful · 2026-09-11 23:15:21 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,023,768 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w412w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf871c2a…17b3
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x61ca6437…2142
0x34b655…2a6f
10 touches
10 conflicts
0x7211ade0…c8c6
0x34b655…2a6f
10 touches
10 conflicts
0x0bf19f18…c22c
0x34b655…2a6f
10 touches
10 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
10 touches
10 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0xdf871c2a42…5f17b3
Audit this contract →
← previous block·next block →recent activity