← previous blocknext block →recent activity
Analyzing
Block #104,201,006
20 transactions · 17 stateful · 2026-09-12 14:16:34 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,201,006 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w110w212w314w416w517w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x404adb8b…d6ec
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x4ccfe55c…de03
0x34b655…2a6f
6 touches
3 conflicts
0x1408e7c7…f324
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
15 conflicts on slot 0x404adb8b17…6ad6ec
Audit this contract →
← previous block·next block →recent activity