← previous blocknext block →recent activity
Analyzing
Block #104,023,294
18 transactions · 18 stateful · 2026-09-11 23:12:56 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,023,294 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w113w114w215w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x316ec1a9…40de
0x34b655…2a6f
6 touches
3 conflicts
0x90f77ef9…4f42
0x34b655…2a6f
6 touches
3 conflicts
0x7ef4ba09…2a25
0x34b655…2a6f
6 touches
3 conflicts
0x30908823…a62d
0x34b655…2a6f
4 touches
1 conflict
0x3accf018…2e8b
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity