← previous blocknext block →recent activity
Analyzing
Block #104,202,043
17 transactions · 14 stateful · 2026-09-12 14:21:51 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,202,043 · 17 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
3w04w17w28w310w411w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe884e676…93a1
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x4bf59d22…00de
0x34b655…2a6f
6 touches
3 conflicts
0xd793c15e…7dba
0x34b655…2a6f
6 touches
3 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
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
21 conflicts on slot 0xe884e6765f…5393a1
Audit this contract →
← previous block·next block →recent activity