← previous blocknext block →recent activity
Analyzing
Block #104,032,367
19 transactions · 19 stateful · 2026-09-11 23:58:56 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,032,367 · 19 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w310w411w512w613w714w817w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x028594e3…157c
0x34b655…2a6f
18 touches
36 conflicts
0x68e5627d…6f8f
0x34b655…2a6f
18 touches
36 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
18 touches
36 conflicts
0x21280422…0930
0x34b655…2a6f
18 touches
36 conflicts
0x0379381b…98af
0x34b655…2a6f
18 touches
36 conflicts
0xf407a637…7cc0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
2 touches
0 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
36 conflicts on slot 0x028594e36e…f6157c
Audit this contract →
← previous block·next block →recent activity