← previous blocknext block →recent activity
Analyzing
Block #104,032,577
19 transactions · 18 stateful · 2026-09-12 00:00:00 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,032,577 · 19 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
5w06w17w28w39w410w511w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8cd993…5c11
0x34b655…2a6f
16 touches
28 conflicts
0x7679e940…f8a3
0x34b655…2a6f
16 touches
28 conflicts
0xd911522b…e960
0x34b655…2a6f
14 touches
21 conflicts
0x2ae559ab…2904
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
28 conflicts on slot 0xfc8cd99357…7e5c11
Audit this contract →
← previous block·next block →recent activity