← previous blocknext block →recent activity
Analyzing
Block #104,322,585
13 transactions · 13 stateful · 2026-09-13 00:33:21 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,322,585 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9084429b…a7f8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf394e6ad…f568
0x34b655…2a6f
4 touches
1 conflict
0x8299fe6c…5752
0x34b655…2a6f
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x282f129e…8f33
0x34b655…2a6f
2 touches
0 conflicts
0x2cef1eff…9f14
0x34b655…2a6f
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
3 conflicts on slot 0x9084429bf7…b9a7f8
Audit this contract →
← previous block·next block →recent activity