← previous blocknext block →recent activity
Analyzing
Block #104,158,357
16 transactions · 16 stateful · 2026-09-12 10:40:10 UTC
Parallelism
38/100
Blocked
56%
Avg conflicts / tx
2.94
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,158,357 · 16 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w28w310w411w512w613w714w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x2c77b5f4…601e
0x34b655…2a6f
12 touches
15 conflicts
0xe66201d4…84f1
0x34b655…2a6f
12 touches
15 conflicts
0x1408e7c7…f324
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
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
36 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity