← previous blocknext block →recent activity
Analyzing
Block #104,165,895
20 transactions · 18 stateful · 2026-09-12 11:18:25 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
1.75
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,165,895 · 20 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
1w02w13w24w05w111w312w414w515w616w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d6da397…6c5c
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x8ac39e10…2cf8
0x34b655…2a6f
8 touches
6 conflicts
0xe7b9eede…2538
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x0630c2e5…b5de
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x5d6da39762…d36c5c
Audit this contract →
← previous block·next block →recent activity